control: tags -1 + moreinfo Hi!
On Mon, Dec 8, 2014 at 9:30 PM, Dmitry Smirnov <only...@debian.org> wrote: > I used all my quota this month and my ISP throttled connection to 512/512. > That's when amule begin to crash -- it works for less than an hour until > "Segmentation fault". I have only KAD enabled and I have a feeling that it may > be related to number of simultaneous connections (although lowering max > simultaneous connections from 900 to 90 did not help). No errors are logged to > console and I tried to run amule under GDB for a while but under GDB it is > slow and problem do not manifest. Without GDB it crashes in 30...60 min. I think that the only way to report it upstream for a fix is to let it run under gdb and wait for it to crash and then generate the required tracebacks. > I think on fast connection I've seen few occasional segfaults in the past but > it was not unusual for amule to last for days and even weeks while now I have > an hour at most. I have an instance of amule running from more than 1week and it is the same version you are reporting this bug againts. > This is on up-to-date Jessie. Just a note: Jessie doesnt include amule, as it was not possible to port it to WX3.0 Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
