Question regarding KDE Crash Handler

[Modestas Vainius]

Hello,

penktadienis 07 Lapkritis 2008, Matthias rašė:
> I tried to start amarok from within gdb, but I have "only 380 MBytes" of
> RAM, and this attempt locked the whole system swapping. Because the
> harddisk is dog slow, swapping doesn't really make sense, so I terminated
> this attempt after watching a few minutes.
If it ends up swapping when you run Amarok under gdb directly, backtrace with 
KDE Crash Handler won't be any easier. It will need the same amount of RAM if 
not more to generate a backtrace.

I recommend to report the steps how to reproduce the bug to Amarok developers 
(which you did).

> Do you have an idea why the Crash Handler can't create the backtrace? Or do
> you have another proposal on how I could get the backtrace?
There may be many reasons. Make sure you installed packages recommended by 
amarok-dbg. 

The most reliable way to get the backtrace is:

$ gdb --args amarok --nofork
(gdb) run
<crash amarok>
(gdb) bt


-- 
Modestas Vainius <modestas at vainius.eu>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20081108/f487ffe0/attachment.pgp