Bug 100102 - Backtraces repoted after crash
Summary: Backtraces repoted after crash
Status: RESOLVED DUPLICATE of bug 100049
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.2
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-23 18:02 UTC by marco marcarelli
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description marco marcarelli 2005-02-23 18:02:30 UTC
Version:           1.2 (using KDE KDE 3.3.2)
Installed from:    Slackware Packages
OS:                Linux

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 5180)]
[New Thread 32769 (LWP 5181)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 5180)]
[New Thread 32769 (LWP 5181)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 5180)]
[New Thread 32769 (LWP 5181)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x419c8ef1 in kill () from /lib/libc.so.6
#7  0x41932bb1 in pthread_kill () from /lib/libpthread.so.0
#8  0x41932f2b in raise () from /lib/libpthread.so.0
#9  0x419c8b24 in raise () from /lib/libc.so.6
#10 0x419ca3fd in abort () from /lib/libc.so.6
#11 0x419c200f in __assert_fail () from /lib/libc.so.6
#12 0x41a8d74c in _dl_close () from /lib/libc.so.6
#13 0x41aac77b in __libc_ptyname2 () from /lib/libc.so.6
#14 0x0000016d in ?? ()
#15 0x41aac7eb in __libc_ptyname2 () from /lib/libc.so.6
#16 0x00000000 in ?? ()
#17 0x00000001 in ?? ()
#18 0x0000004f in ?? ()
#19 0x00000054 in ?? ()
#20 0x00000003 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00000000 in ?? ()
#23 0x00000000 in ?? ()
#24 0x00000007 in ?? ()
#25 0x0000000c in ?? ()
#26 0x41933e70 in __pthread_lock () from /lib/libpthread.so.0
Comment 1 Mark Kretschmann 2005-02-23 18:24:17 UTC
Although the backtrace is hardly useful, from what I see it is a dupe of another report. Which is basically a dupe of yet another report ;) A xine library problem.


*** This bug has been marked as a duplicate of 100049 ***