| Summary: | [Regression] TDE Crash Handler can't generate backtraces | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Kristopher <gamrat.kristopher> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | bugwatch, gamrat.kristopher, kb9vqf, michele.calgaro, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: |
~/.xsession-errors
Screenshot of crash handler Debug DrKonqui backtrace generator |
||
|
Description
Kristopher
2014-12-01 20:03:50 CST
Interesting, seeing as I just used the crash handler earlier today to submit an R14 RC2 crash report on Ubuntu Trusty. What version of Linux are you testing this on? Does this bug occur with all crashed programs or more often with specific programs? Thanks! Tim (In reply to Timothy Pearson from comment #1) > Interesting, seeing as I just used the crash handler earlier today to submit > an R14 RC2 crash report on Ubuntu Trusty. > > What version of Linux are you testing this on? Does this bug occur with all > crashed programs or more often with specific programs? > > Thanks! > > Tim I am using Debian Wheezy using the R14 nightlies. This happens with all TDE applications, but not non-TDE applications (in fact, the TDE crash handler never appears for non-TDE applications, I don't know if that's to be expected). Interesting bug. I also never had any problem with the crash handler. (In reply to Michele Calgaro from comment #3) > Interesting bug. > I also never had any problem with the crash handler. I'm wondering if it's Debian specific at the moment; I know Ubuntu broke the crash handler a long time ago with a ptrace lockdown so it's possible Debian did something similar at some point. In any case it would be helpful to have DrKonqui give more information on why it can't generate the backtrace instead of the rather unhelpful message it has now. I can confirm that also have not noticed this problem - Debian Wheezy. It says something useful to ~/.xsession-errors? Created attachment 2377 [details] ~/.xsession-errors Near the end, you can see where I produce a crash I reported in bug 2226. It's surrounding a bunch of messages pertaining to bad windows parameters. I doubt that provides any information helpful to the TDE Crash Handler. Without additional information, and since none of our developers can reproduce the glitch, I don't think we can fix this for R14.0.0. Marking for investigation/resolution in R14.0.1. Created attachment 2383 [details]
Screenshot of crash handler
I don't know if it will help, but I took a screenshot of the Crash Handler's inability to produce backtraces. You can see Synaptic open and showing the green "this is installed" squares next to the -dbg packages for the TDE components I have installed, as well as Konsole displaying a gdb backtrace of the same crash that summoned the Crash Handler.
(In reply to Kristopher from comment #8) > Created attachment 2383 [details] > Screenshot of crash handler > > I don't know if it will help, but I took a screenshot of the Crash Handler's > inability to produce backtraces. You can see Synaptic open and showing the > green "this is installed" squares next to the -dbg packages for the TDE > components I have installed, as well as Konsole displaying a gdb backtrace > of the same crash that summoned the Crash Handler. Well, that might help actually. When you said couldn't generate backtraces I assumed you meant the one-line text in DrKonqui that basically says "couldn't generate backtrace" or similar. What you have there is something different; DrKonqui trying to weed out invalid backtraces and probably regexp-matching something in your dump that it shouldn't be. Created attachment 2389 [details]
Debug DrKonqui backtrace generator
I need some additional information to properly debug this issue. Can you apply the attached patch to tdebase, rebuild/reinstall tdebase, log out/log in, then cause another crash and attach the output of your ~/.xsession_errors file that contains the new [DrKonqui DEBUG] lines?
Thanks!
The TDE Crash Handler seems to work in a VM on a fresh install of Debian Wheezy + TDE. As mentioned by Timothy in bug #2240, this *could* be caused by a conflict between the libs/binaries and debug symbols, as one of the backtraces I've attached to that bug report mentions a CRC mismatch in the debug symbols. I can confirm that I have been keeping both the -dbg packages and the regular TDE packages up-to-date, I have allowed all TDE packages to be upgrade during all runs "apt-get dist-upgrade". As seen in bug 2167 comment 16 , I am now seeing this issue on CentOS 7, however the backtrace attached there does *not* mention any mismatches in any CRC (or other) checksums. In addition, it's hard to tell if the issue there is from TDE itself or from the fact that I've installed debug symbols from non-TDE packages that could be interfering in some way with TDE. |