GNOME Bugzilla – Bug 393702
Please visit http://live.gnome.org/GettingTraces for more information!
Last modified: 2009-03-02 00:37:20 UTC
Dear bug reporter, unfortunately, the stack trace of your report is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I have followed the instructions step by step, eog-dbgsym is reported as installed by dpkg, but I keep getting here whenever I try to send a crash report of EOG.
Control Center crashed while selecting a different mouse icon. This SUSE install is hours fresh with little personalization and only default package install. In the background I had the Software Install program open and had only selected a couple of programs for install (adobe reader), but had not installed yet. Bug details are: -------------- Memory status: size: 91119616 vsize: 0 resident: 91119616 share: 0 rss: 4714496 rss_rlim: 0 CPU usage: start_time: 1170753227 rtime: 0 utime: 299 stime: 0 cutime:290 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nm-applet' (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) (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 -1226500416 (LWP 4099)] (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) 0xb7f92410 in ?? ()
+ Trace 108477
Thread 1 (Thread -1226500416 (LWP 4099))
Lame. Bug buddy sent me here, but clearly bug report has nothing do to with me: --------------------------------------------------------------------- A bug report detailing your software crash has been sent to GNOME. This information will allow the developers to understand the cause of the crash and prepare a solution for it. You may be contacted by a GNOME developer if more details are required about the crash. You can view your bug report and follow its progress with this URL: http://bugzilla.gnome.org/show_bug.cgi?id=393702 --------------------------------------------------------------------- Open SUSE 10.2
Bryce, it's not lame - if you would just read comment #0 here you would know what to do to get better support and to not get redirected to this report telling you to provide a better stacktrace.
The interesting thing is that I *did* enable all things for a stack trace (I'm on Gentoo, so that means setting the "splitdebug" feature and the -ggdb option), and I'm still getting traces without symbols. Already reported it to them (see http://bugs.gentoo.org/show_bug.cgi?id=213389), but over there no-one knows yet why this happens. Now with another crash I got redirected here. Ideas, anyone?
I'm being directed here for a gnome-sudoku bug that *does* include python stack trace: Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-04-15 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- if self.select_game():
+ Trace 195513
ret = fun(ui,*args,**kwargs)
choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower)
self.setup_dialog()
self.make_saved_game_model()
sudoku.sudoku_grid_from_string(g['game'].split('\n')[1].replace(' ','')).grid,
assert(len(s)<=GROUP_SIZE**2) AssertionError -------------------------------------------------- Traceback (most recent call last):
start_game()
main.start_game()
u = UI()
if self.select_game():
assert(len(s)<=GROUP_SIZE**2) AssertionError
I see there's already an open report for my sudoku problem, but there's obviously another problem with Bug Buddy not noticing the python stack trace.
The problem is in the saved games. Somehow instead of writing 0 sometimes it stores a None as a field value. This makes the size of the puzzle greater than 9**2 which results in the AssertionError in sudoku_grid_from_string. I'm not sure which function is causing these None values (but I'd guess it's function that's supposed to return a 0 in certain cases but exits without returning a value). Maybe it happens when clearing a tracker, seems to be when I get this.
I got it without using anything other than notes. I ended up in a dead end (obviously I had made a logical mistake somewhere) and gave up. When I returned I got the crash message with a 'none' in the array. Chris
Created attachment 119977 [details] Trace from BugBuddy re Gnome Sudoku problem
Phil Kuhn: What's the context? Why do you attach it here? Your trace is bug 537089.
(In reply to comment #10) > Phil Kuhn: What's the context? Why do you attach it here? Your trace is bug > 537089. > Sorry, I'm a noob to bug reporting. Until your reply, the only bug number I remember seeing is the one to which I attached the listing.
How do I get Sudoku to run again? After the crash, I get a Bug Report screen every time I try to run it. I submit the report, and get an email that the stack trace is missing, but Bug Buddy is supposedly sending a trace (similar to that in comment 6). I've tried uninstalling and reinstalling the gnome games package.
(In reply to comment #12) > How do I get Sudoku to run again? After the crash, I get a Bug Report screen > every time I try to run it. I submit the report, and get an email that the > stack trace is missing, but Bug Buddy is supposedly sending a trace (similar to > that in comment 6). > > I've tried uninstalling and reinstalling the gnome games package. This is not a help forum. This page says "Please check http://live.gnome.org/GettingTraces instead."
Well, I take it then that the bug is in Bug Buddy itself. It is sending me to this page after sending the stack trace, which is then sent back to me with the message that it needs the stack trace, which is attached to the message coming back, and you say to visit "Getting Traces" instead...
It's not a bug. Bug-buddy does not even send the stacktrace because the stacktrace is useless, instead it "fakes" the answer because we cannot easily display a message in bug-buddy telling you to install debug packages to provide a useful stacktrace. Once the stacktrace is useful it will be sent and receive a "real" bug number.
With all due respect, Andre, I think you are completely wrong. For failed assertion in a python program, a python backtrace is provided. A gdb backtrace of python, glib, gtk, etc. is going to be completely useless. Not recognizing this is a bug in Bug Buddy.
Oh, sudoku is in python? OK... "gnome-sudoku -v" starts the debug mode.
Unsubscribing since I don't see any "real" activity on this bug report. Might submit a patch myself if I run into this bug again.