PDA

View Full Version : slimproto backtrace, due to musicmagic



kdf
2005-07-30, 11:02
Using:
../slimserver.pl --d_prefs --d_parse --d_slimproto --d_info

I get a backtrack during startup. I'm wondering if anyone can give me a clue
what this means (I'm not into slimproto). Is it just a harmless debug-caused
trace, or is the musicmagic http api interfering with slimproto?

-kdf


005-07-30 10:53:27.7728 Writing out prefs in /etc/slimserver.conf
2005-07-30 10:53:28.0668 *************stream called: q paused: format: url:
2005-07-30 10:53:28.0676 Backtrace:

frame 0: Slim::Player::Squeezebox::stream
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox.pm line 195
)
frame 1: Slim::Player::Squeezebox::stop
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox2.pm line 597)
frame 2: Slim::Player::Squeezebox2::stop
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox.pm line 81)
frame 3: Slim::Player::Squeezebox::reconnect
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networking/Slimproto.pm li
ne 337)
frame 4: Slim::Networking::Slimproto::process_slimproto_fra me
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networkin
g/Slimproto.pm line 236)
frame 5: Slim::Networking::Slimproto::client_readable
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networking/Select
..pm line 115)
frame 6: Slim::Networking::Select::select (./slimserver.pl line 667)
frame 7: main::idleStreams
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Protocols/HTTP.pm line
310)
frame 8: Slim::Player::Protocols::HTTP::content
(/mnt/mandrake/usr/local/slimserver/trunk/Plugins/MusicMagic/Plugin.pm
line 132)
frame 9: Plugins::MusicMagic::Plugin::initPlugin
(/mnt/mandrake/usr/local/slimserver/trunk/Plugins/MusicMagic/Plugin.p
m line 77)
frame 10: Plugins::MusicMagic::Plugin::enabled
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line
171)
frame 11: Slim::Buttons::Plugins::canPlugin
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 217
)
frame 12: Slim::Buttons::Plugins::addPlugin
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 140
)
frame 13: Slim::Buttons::Plugins::initPlugins
(/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 5
0)
frame 14: Slim::Buttons::Plugins::init (./slimserver.pl line 555)
frame 15: main::start (./slimserver.pl line 577)
frame 16: main::main (./slimserver.pl line 1176)

2005-07-30 10:53:28.0688 starting with decoder with format: m autostart: 0
threshold: 255 samplesize: ? samplerate: ? end
ian: ? channels: ?
2005-07-30 10:53:28.0690 sending strm frame of length: 76 request string:
GET /stream.mp3?player=20:09:01:01:00:20 HTTP/1.0

Triode
2005-07-30, 11:32
Looks to me that turning on slimproto debug forces a backtrace to be called:

>From Slim::Player::Squeezebox::stream

if ($client->opened()) {
$::d_slimproto && msg("*************stream called: $command paused: $paused format: $format url: $url\n");
$::d_slimproto && bt();

So nothing to worry about..

Adrian
----- Original Message -----
From: "kdf" <slim-mail (AT) deane-freeman (DOT) com>
To: "Slim Devices Developers" <developers (AT) lists (DOT) slimdevices.com>
Sent: Saturday, July 30, 2005 7:02 PM
Subject: [Developers] slimproto backtrace, due to musicmagic


> Using:
> ./slimserver.pl --d_prefs --d_parse --d_slimproto --d_info
>
> I get a backtrack during startup. I'm wondering if anyone can give me a clue
> what this means (I'm not into slimproto). Is it just a harmless debug-caused
> trace, or is the musicmagic http api interfering with slimproto?
>
> -kdf
>
>
> 005-07-30 10:53:27.7728 Writing out prefs in /etc/slimserver.conf
> 2005-07-30 10:53:28.0668 *************stream called: q paused: format: url:
> 2005-07-30 10:53:28.0676 Backtrace:
>
> frame 0: Slim::Player::Squeezebox::stream
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox.pm line 195
> )
> frame 1: Slim::Player::Squeezebox::stop
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox2.pm line 597)
> frame 2: Slim::Player::Squeezebox2::stop
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox.pm line 81)
> frame 3: Slim::Player::Squeezebox::reconnect
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networking/Slimproto.pm li
> ne 337)
> frame 4: Slim::Networking::Slimproto::process_slimproto_fra me
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networkin
> g/Slimproto.pm line 236)
> frame 5: Slim::Networking::Slimproto::client_readable
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networking/Select
> .pm line 115)
> frame 6: Slim::Networking::Select::select (./slimserver.pl line 667)
> frame 7: main::idleStreams
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Protocols/HTTP.pm line
> 310)
> frame 8: Slim::Player::Protocols::HTTP::content
> (/mnt/mandrake/usr/local/slimserver/trunk/Plugins/MusicMagic/Plugin.pm
> line 132)
> frame 9: Plugins::MusicMagic::Plugin::initPlugin
> (/mnt/mandrake/usr/local/slimserver/trunk/Plugins/MusicMagic/Plugin.p
> m line 77)
> frame 10: Plugins::MusicMagic::Plugin::enabled
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line
> 171)
> frame 11: Slim::Buttons::Plugins::canPlugin
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 217
> )
> frame 12: Slim::Buttons::Plugins::addPlugin
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 140
> )
> frame 13: Slim::Buttons::Plugins::initPlugins
> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 5
> 0)
> frame 14: Slim::Buttons::Plugins::init (./slimserver.pl line 555)
> frame 15: main::start (./slimserver.pl line 577)
> frame 16: main::main (./slimserver.pl line 1176)
>
> 2005-07-30 10:53:28.0688 starting with decoder with format: m autostart: 0
> threshold: 255 samplesize: ? samplerate: ? end
> ian: ? channels: ?
> 2005-07-30 10:53:28.0690 sending strm frame of length: 76 request string:
> GET /stream.mp3?player=20:09:01:01:00:20 HTTP/1.0
>
>
>
>
>
>

Triode
2005-07-30, 11:37
Should have said that the only reason you see the plugin in the stack trace is that HTTP.pm calls idleStreams which then calls
select, so it appears that the plugin is calling it in some way, but actually it is main::idleStreams which is a light weight
version of the main loop which is there to keep streaming going [but also new slimproto connections] in the middle of heavy activity
such as HTTP. (but you probably knew that)

>> frame 0: Slim::Player::Squeezebox::stream
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox.pm line 195
>> )
>> frame 1: Slim::Player::Squeezebox::stop
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox2.pm line 597)
>> frame 2: Slim::Player::Squeezebox2::stop
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Squeezebox.pm line 81)
>> frame 3: Slim::Player::Squeezebox::reconnect
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networking/Slimproto.pm li
>> ne 337)
>> frame 4: Slim::Networking::Slimproto::process_slimproto_fra me
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networkin
>> g/Slimproto.pm line 236)
>> frame 5: Slim::Networking::Slimproto::client_readable
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Networking/Select
>> .pm line 115)
>> frame 6: Slim::Networking::Select::select (./slimserver.pl line 667)
>> frame 7: main::idleStreams
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Player/Protocols/HTTP.pm line
>> 310)
>> frame 8: Slim::Player::Protocols::HTTP::content
>> (/mnt/mandrake/usr/local/slimserver/trunk/Plugins/MusicMagic/Plugin.pm
>> line 132)
>> frame 9: Plugins::MusicMagic::Plugin::initPlugin
>> (/mnt/mandrake/usr/local/slimserver/trunk/Plugins/MusicMagic/Plugin.p
>> m line 77)
>> frame 10: Plugins::MusicMagic::Plugin::enabled
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line
>> 171)
>> frame 11: Slim::Buttons::Plugins::canPlugin
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 217
>> )
>> frame 12: Slim::Buttons::Plugins::addPlugin
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 140
>> )
>> frame 13: Slim::Buttons::Plugins::initPlugins
>> (/mnt/mandrake/usr/local/slimserver/trunk/Slim/Buttons/Plugins.pm line 5
>> 0)
>> frame 14: Slim::Buttons::Plugins::init (./slimserver.pl line 555)
>> frame 15: main::start (./slimserver.pl line 577)
>> frame 16: main::main (./slimserver.pl line 1176)
>>
>> 2005-07-30 10:53:28.0688 starting with decoder with format: m autostart: 0
>> threshold: 255 samplesize: ? samplerate: ? end
>> ian: ? channels: ?
>> 2005-07-30 10:53:28.0690 sending strm frame of length: 76 request string:
>> GET /stream.mp3?player=20:09:01:01:00:20 HTTP/1.0

kdf
2005-07-30, 14:45
On 30-Jul-05, at 11:32 AM, Triode wrote:

> Looks to me that turning on slimproto debug forces a backtrace to be
> called:
>
>> From Slim::Player::Squeezebox::stream
>
> if ($client->opened()) {
> $::d_slimproto && msg("*************stream called: $command paused:
> $paused format: $format url: $url\n");
> $::d_slimproto && bt();
> So nothing to worry about..
>

heh, thanks :)

I was being horribly lazy today and not looking it up. I've been
having the most amazing electronics problems this weekend, including
the loss of two surge protectors inside of the same minute, and waking
every morning to slimserver locked at 98% cpu. I saw that and just
didn't want to lose another hour digging when I could post, go do my
errands and count on having the answer anyway by the time I got back..

ta mate!
-kdf