https://bugzilla.novell.com/show_bug.cgi?id=825339 https://bugzilla.novell.com/show_bug.cgi?id=825339#c17 --- Comment #17 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2013-07-05 15:26:45 UTC --- (In reply to comment #16)
(In reply to comment #15)
yes, working with gdb is not easy. I just have no idea how to help you in a different way since I cannot reproduce it.
That's ok, as long as you tell me what to do.
Anyway, there is still stuff missing. Did you really read all of the wiki article I've linked?
No, I said above that I have no idea what wiki you are talking about. There is no link here.
Please reread comment 9 There is a link
Ok, it crashed, but bt says there is no backtrace. Notice that at the crash point TB does not crash completely, instead it pops up the dialog to send crash info upstream. I typed "bt" before and after clicking send on that dialog.
You can also export MOZ_CRASHREPORTER=0 to avoid the Mozilla crashreporter but I don't think that makes a difference.
This is what I got:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7fb7740 (LWP 4973)] 0x00007fffef11b486 in IA__gdk_window_get_toplevel (window=0x7fffceb0d100) at gdkwindow.c:2414 2414 gdkwindow.c: No such file or directory. (gdb) continue
instead of "continue" I would have expected "bt" directly after the SIGSEGV. Could you please try that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.