Bug 339476

Summary:	[frameworks] Not getting proper backtraces with drkonqi
Product:	[Applications] drkonqi	Reporter:	Bhushan Shah <bshah>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	mail, martin.sandsmark
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
URL:	https://sourceware.org/bugzilla/show_bug.cgi?id=17446
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

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