pkg kde talk - Nov 2008 - Question regarding KDE Crash Handler

Hi!

I have a reproducable crash of Amarok Beta 3, I installed the amarok-dbg 
package in order to create a backtrace. From the KDE Crash Handler I''m
getting
the following note:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents 
creation of proper backtraces, or the stack frame was seriously corrupted in 
the crash.

Obviously I have gdb installed.

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.

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?

regards
matthias

On Friday 07 November 2008 10:45:18 Matthias wrote:
> Hi!
>
> I have a reproducable crash of Amarok Beta 3, I installed the amarok-dbg
> package in order to create a backtrace. From the KDE Crash Handler
I''m
> getting the following note:
Is there a way to reproduce the problem? 

Nontheless, Amarok is Beta, so crashed are spected.

-- 
La ciencia sin la religi?n es renga,
la religi?n sin la ciencia es ciega.
 Albert Einstein

Lisandro Dami?n Nicanor P?rez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

-------------- 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/20081107/8dbb9cf9/attachment.pgp

Hi,
> This backtrace appears to be of no use.
> This is probably because your packages are built in a way which prevents
> creation of proper backtraces, or the stack frame was seriously corrupted
> in the crash.
Afair Amarok is a "unique application", so only one instance even if
you
run "amarok" multiple times.
Try to close it, then run "amarok --nofork &" and wait for it to
crash.

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

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