![]() |
0.95 keeps crashing 0.95 keeps crashing pretty much says it all: I installed the Debian build at around 3 this morning, it's now 5 and it has seg faulted 5 times. 0.93 never crashed very often, but eventually the powers that be seemed to gang up on it........ There doesn't seem any consistency in the crashing. The last reads: //snip Outgoing b/w EMA = 256 bytes/s Incoming b/w EMA = 4239 bytes/s 05/01/05 05:31:45 (MESSAGE): PARQ UL: Not sending QUEUE command due to another pending QUEUE command for ip: 24.132.6.5 05/01/05 05:31:45 (MESSAGE): PARQ UL: Not sending QUEUE command due to another pending QUEUE command for ip: 24.132.6.5 bsched_timer(out): delay=1009 (EMA=1010), b/w=0 (EMA=3), overused=-6199 (EMA=-6196) stolen=0 (EMA=0) unwritten=0 capped=0 (0) used 0/0 -> b/w delta=-7541904, max=6205, slot=0, first=0 (target 6144 B/s, 0 slots, real 0.00 B/s) Outgoing b/w EMA = 252 bytes/s Incoming b/w EMA = 4232 bytes/s 05/01/05 05:31:46 (MESSAGE): PARQ UL: Not sending QUEUE command due to another pending QUEUE command for ip: 24.132.6.5 05/01/05 05:31:46 (MESSAGE): PARQ UL: Not sending QUEUE command due to another pending QUEUE command for ip: 24.132.6.5 Query with extensions: track > HUGE (token=3) 0 bytes Share HIT 45 files 'track' req_speed=224 ttl=0 hops=4 Segmentation fault john@niglo:~$ Ideas? |
Re: 0.95 keeps crashing (coredump + backtrace included) Quote:
-Doptimize="-O2" to -Doptimize="-g -O2" And rpmbuild -ba 'ing it. After running for a random length of time... This is after I've been running 0.93.4-1 RPM for many many months, with nary a hiccup. Developers, please contact me for more info, if needed. Code: (gdb) target core core |
Before I do the bad thing and install Limewire :( (which will mean trying to get the 95% and 90% ile files I've got through older versions of gtk-gnutella into a format Limewire will accept as its own) can anyone come up with a script to keep gtk-gnutella up? I'm thinking of a cron job every 5 seconds to check if gtk-gnutella is up and if not to launch it again. Anyone wanting debugging "dumps" just ask -- I've more than enough! :rolleyes: |
Hi, The core dumps don't really look that useable. Sorry, try to compile with -g3 only (so no -O optimisation). Then when it crashes do a bt full. If you don't get a core dump, > ulimit -c unlimited should do the trick. After it dumps do a: gdb gtk-gnutella core and enter 'bt full' Without a good backtrace the problem will be very hard to spot. |
Wierder and wierder. I restarted it at about 4pm, left it unattended and on returning from work at 3am it's still up and downloading. Very odd. Possible explanation is that it was something on one of the hosts which was causing my client to crash. >> Later ........Now 22 hours uptime -- what's noticeable is that I seem to have more alive connections than with the older version. Oh joy! One of the things I've been downloading for the last 3 weeks is just about finished. :D |
For the past few days, I kept running the version that got installed by the rpm -- and kept wondering why I wasn't getting more useful results =) (The executable is stripped before RPM packaging.) Here's a dump from running the src/gtk-gnutella under gdb (I hope that aspect of running it doesn't mess up the bug behavior) -- I can run it and get a regular core to target if anyone wants. Cheers, buckaro0 Code: (gdb) bt |
This is the same bug as this one: https://sourceforge.net/tracker/inde...67&atid=104467 It's fixed in CVS. |
All times are GMT -7. The time now is 12:46 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.