PDA

View Full Version : backtrace getting logged in rev 2349 - slimlog.txt(1/1)



Lars Kellogg-Stedman
2005-03-07, 16:21
Whenever slimserver (currently rev 2349, but this has been true for
several weeks) starts up, it immediately logs a backtrace followed by
the text, "Here's the problem.", and then a dump of perl code from
Slimproto.pm.

I've attached a log extract to this message.

Everything appears to work correctly despite this message. Any idea
what's going on here?

-- Lars


2005-03-07 18:13:56.1825 Backtrace:
frame 0: Slim::Utils::Misc::assert (/oddbit/home/slimserver/slim/server//Slim/Networking/Slimproto.pm line 182)
frame 1: Slim::Networking::Slimproto::client_readable (/oddbit/home/slimserver/slim/server//Slim/Networking/Select.pm line 116)
frame 2: Slim::Networking::Select::select (/oddbit/home/slimserver/slim/server/slimserver.pl line 583)
frame 3: main::idleStreams (/oddbit/home/slimserver/slim/server//Slim/Player/Protocols/HTTP.pm line 351)
frame 4: Slim::Player::Protocols::HTTP::content (/oddbit/home/slimserver/slim/server//Plugins/RssNews.pm line 420)
frame 5: Plugins::RssNews::getFeedXml (/oddbit/home/slimserver/slim/server//Plugins/RssNews.pm line 472)
frame 6: Plugins::RssNews::retrieveNews (/oddbit/home/slimserver/slim/server//Plugins/RssNews.pm line 590)
frame 7: Plugins::RssNews::autoScrollTimer (/oddbit/home/slimserver/slim/server//Plugins/RssNews.pm line 762)
frame 8: Plugins::RssNews::setScreensaverRssNewsMode (/oddbit/home/slimserver/slim/server//Slim/Buttons/Common.pm line 1045)
frame 9: Slim::Buttons::Common::pushMode (/oddbit/home/slimserver/slim/server//Slim/Buttons/ScreenSaver.pm line 106)
frame 10: Slim::Buttons::ScreenSaver::screenSaver (/oddbit/home/slimserver/slim/server//Slim/Player/Player.pm line 149)
frame 11: Slim::Player::Player::init (/oddbit/home/slimserver/slim/server//Slim/Networking/Slimproto.pm line 327)
frame 12: Slim::Networking::Slimproto::process_slimproto_fra me (/oddbit/home/slimserver/slim/server//Slim/Networking/Slimproto.pm line 233)
frame 13: Slim::Networking::Slimproto::client_readable (/oddbit/home/slimserver/slim/server//Slim/Networking/Select.pm line 116)
frame 14: Slim::Networking::Select::select (/oddbit/home/slimserver/slim/server/slimserver.pl line 569)
frame 15: main::idle (/oddbit/home/slimserver/slim/server/slimserver.pl line 512)
frame 16: main::main (/oddbit/home/slimserver/slim/server/slimserver.pl line 1051)
Here's the problem. /oddbit/home/slimserver/slim/server//Slim/Networking/Slimproto.pm, line 182:
172 if ($parser_state{$s} eq 'OP') {
173 $bytes_remaining = 4 - length($inputbuffer{$s});
174 assert ($bytes_remaining <= 4);
175 } elsif ($parser_state{$s} eq 'LENGTH') {
176 $bytes_remaining = 4 - length($inputbuffer{$s});
177 assert ($bytes_remaining <= 4);
178 } else {
179 assert ($parser_state{$s} eq 'DATA');
180 $bytes_remaining = $parser_framelength{$s} - length($inputbuffer{$s});
181 }
182 assert ($bytes_remaining > 0);
183
184 $::d_slimproto_v && msg("attempting to read $bytes_remaining bytes\n");
185
186 my $indata;
187 my $bytes_read = $s->sysread($indata, $bytes_remaining);
188
189 if (!defined($bytes_read) || ($bytes_read == 0)) {
190 if ($total_bytes_read == 0) {
191 $::d_slimproto && msg("Slimproto half-close from client: ".$ipport{$s}."\n");
192 slimproto_close($s);
getpeername() on closed socket GEN5 at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/IO/Socket.pm line 206.
getpeername() on closed socket GEN5 at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/IO/Socket.pm line 206.

Dave Cohen
2005-03-08, 19:37
Lars,

I recall seeing this myself, but a recent update made it disappear for
me. Are you still seeing it?

I was seeing it quite a few times, not just on startup.

-Dave



On Mon, Mar 07, 2005 at 06:21:52PM -0500, Lars Kellogg-Stedman wrote:
> Whenever slimserver (currently rev 2349, but this has been true for
> several weeks) starts up, it immediately logs a backtrace followed by
> the text, "Here's the problem.", and then a dump of perl code from
> Slimproto.pm.
>
> I've attached a log extract to this message.
>
> Everything appears to work correctly despite this message. Any idea
> what's going on here?
>
> -- Lars
>

> 2005-03-07 18:13:56.1825 Backtrace:
> frame 0: Slim::Utils::Misc::assert (/oddbit/home/slimserver/slim/server//Slim/Networking/Slimproto.pm line 182)
> frame 1: Slim::Networking::Slimproto::client_readable (/oddbit/home/slimserver/slim/server//Slim/Networking/Select.pm line 116)
> frame 2: Slim::Networking::Select::select (/oddbit/home/slimserver/slim/server/slimserver.pl line 583)
> frame 3: main::idleStreams (/oddbit/home/slimserver/slim/server//Slim/Player/Protocols/HTTP.pm line 351)

[snip]

> 175 } elsif ($parser_state{$s} eq 'LENGTH') {
> 176 $bytes_remaining = 4 - length($inputbuffer{$s});
> 177 assert ($bytes_remaining <= 4);
> 178 } else {
> 179 assert ($parser_state{$s} eq 'DATA');
> 180 $bytes_remaining = $parser_framelength{$s} - length($inputbuffer{$s});
> 181 }
> 182 assert ($bytes_remaining > 0);
> 183
> 184 $::d_slimproto_v && msg("attempting to read $bytes_remaining bytes\n");
> 185
> 186 my $indata;
> 187 my $bytes_read = $s->sysread($indata, $bytes_remaining);
> 188
> 189 if (!defined($bytes_read) || ($bytes_read == 0)) {

Lars Kellogg-Stedman
2005-03-08, 21:56
> I recall seeing this myself, but a recent update made it disappear for
> me. Are you still seeing it?

Hmm, it looks like one of today's many updates has resolved this problem.

-- Lars