| Summary: | gnome-extra/bug-buddy-2.20.1 gives backtrace without symbols after gnome-extra/sensors-applet-1.7.12 crash despite splitdebug | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Gerben Vos <gpvos+gnt> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | sensort-applet bug report file as generated by bug-buddy | ||
|
Description
Gerben Vos
2008-03-14 14:08:41 UTC
Created attachment 146123 [details]
sensort-applet bug report file as generated by bug-buddy
Argh, mixed up two lines in the description. This should of course be: Actual Results: A bugreport file containing a backtrace without symbols. Expected Results: A bugreport file containing a backtrace with symbols. "Note that I have recompiled xorg and some other X libraries." I meant to say "Note that I have recompiled xorg and some other X libraries, but haven't restarted X yet." Weird, bug-buddy picks up symbols fine here, but it's gnome 2.22. Maybe it's been fixed in the newer version. Gnome 2.22 has been unmasked, could you please try again with a newer bug-buddy? I've used bug-buddy several times in the past few weeks to get stack traces so I know 2.22 works (at least for me). Thanks OK, I have installed bug-buddy 2.22 (not yet gnome 2.22). I can't guarantee that it will trigger soon, of course. Actually, my current theory about this is that it was caused by some libraries on the file system not being the same as the libraries in the crashed process (see comment #3), which confused gdb and therefore inhibited the stack trace. I have rebooted in the meantime, so the problem may be gone. If you want, you may close it as "cannot reproduce". How about NEEDINFO for now. If you cannot reproduce it, someone will find it in a sweep later and close it. |