On Tue, 9 Dec 2014 00:33:20 Sandro Tosi wrote:
> I'm sorry, the way upstream wants backtraces is running these gdb commands:
>
> bt
> bt full
> thread apply all bt
OK, no worries, it didn't take too long before I got opportunity to get
another backtrace :
(gdb) bt
#0 g_source_unref_interna
On Tue, Dec 9, 2014 at 12:06 AM, Dmitry Smirnov wrote:
> On Mon, 8 Dec 2014 22:51:28 Sandro Tosi wrote:
>> no well maybe it is known but just mention it SIGSEGV without proving
>> even a location memory or so it is hard to say if someone else already
>> spotted it or now
>>
>> > Thanks, I'll run i
On Mon, 8 Dec 2014 22:51:28 Sandro Tosi wrote:
> no well maybe it is known but just mention it SIGSEGV without proving
> even a location memory or so it is hard to say if someone else already
> spotted it or now
>
> > Thanks, I'll run it in GDB and try to wait long enough for it to crash.
Here i
On Mon, Dec 8, 2014 at 10:46 PM, Dmitry Smirnov wrote:
> On Mon, 8 Dec 2014 21:53:49 Sandro Tosi wrote:
>> 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.
>
> So it is not a known bug...
On Mon, 8 Dec 2014 21:53:49 Sandro Tosi wrote:
> 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.
So it is not a known bug...
Thanks, I'll run it in GDB and try to wait long enough for it to
control: tags -1 + moreinfo
Hi!
On Mon, Dec 8, 2014 at 9:30 PM, Dmitry Smirnov 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
6 matches
Mail list logo
