Bug 339476 - [frameworks] Not getting proper backtraces with drkonqi
Summary: [frameworks] Not getting proper backtraces with drkonqi
Status: RESOLVED UPSTREAM
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL: https://sourceware.org/bugzilla/show_...
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-28 14:53 UTC by Bhushan Shah
Modified: 2014-09-30 12:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bhushan Shah 2014-09-28 14:53:58 UTC 
I am not getting proper backtraces with Dr. Konqi on Plasma 5 system.

All I am getting is, 

Application: plasmashell (plasmashell), signal: Aborted
[Current thread is 1 (process 1047)]

Thread 1 (process 1047):
#0  0x00007f88ee19a77d in ?? ()
#1  0x0000000000000000 in ?? ()

and if I manually use gdb. the backtraces are fine... so I am wondering whats wrong..

gdb version:
GNU gdb (GDB) 7.8

kcrash and plasma-workspace from git master

Reproducible: Always

Steps to Reproduce:
1. Crash any application
2.
3.

Actual Results:  
Dr. Konqi window pops up, after selecting developer information tab you get backtrace mentioned above

Expected Results:  
Proper backtrace is generated.
Comment 1 Martin Sandsmark 2014-09-30 12:47:37 UTC 
this is because of a bug in gdb: https://sourceware.org/bugzilla/show_bug.cgi?id=17446