Forums » Bugs

Bug reporter not popping up

Oct 22, 2009 ladron link
The Vendetta client crashes on me every so often. It isn't unbearable and I'm not too upset about it or anything.

However, I've seen various devs mentioning a "bug reporter dialog" in a lot of other crash-related bug posts. I've never seen such a dialog, and it seems like most people who experience crashes don't see it either.

Specific Problem: Crash report dialog does not appear upon program crash

Steps to reproduce: Run the client until it crashes. Notice that the crash report dialog didn't appear.

Expected behavior: Evidently, there's supposed to be a crash report dialog.

Just making sure you guys were aware of this.
Oct 23, 2009 momerath42 link
What platform are you on?
Oct 23, 2009 ladron link
Oh, sorry, I thought I had included that information in my previous post. Must have accidentally deleted it.

I'm using the 64-bit Linux build.
Oct 24, 2009 momerath42 link
We think this is fixed. Please let us know if you experience another crash where the reporter doesn't come up.
Oct 24, 2009 ladron link
Will do, thanks.
Nov 01, 2009 ladron link
Just FYI, I experienced another client crash with no bug reporter (and nothing noteworthy in the error log - it just had some chat logs and then stopped logging). I think both Gnome and KDE have some sort of 'crash handler' daemon built in, does VO expect to find some such daemon? I just use a simple window manager, so I would not have anything like that running. Just kicking some ideas around.

In case any of this is relevant, I'm using the 64 bit build on arch linux with an ATI graphics card using the catalyst drivers, and I use either fluxbox or awesome wm.
Nov 01, 2009 mr_spuck link
Do you start the game from a console? Libc likes to kill processes with SIGABRT then print the backtrace to the console. Maybe the game is only trapping SIGSEGV.
Nov 01, 2009 incarnate link
I don't know what we're trapping, specifically, but in answer to ladron's question, all our crash-handling and traceback functionality is built into the game and updater.
Nov 01, 2009 mr_spuck link
Nevermind, it seems to do both. It was just a shot in the dark.
Nov 02, 2009 ladron link
Is there anything else you'd like me to try to help debug this? I personally am not incredibly bothered by the lack of a crash reporter, so if you guys don't really care either I'll drop the issue, but if my setup is potentially exposing some bug that you'd like to fix I'll do my best to help find it.
Nov 04, 2009 mr_spuck link
I've crashed the game under a couple of linux distros running in VirtualBox. I triggered the crashes with pkill -SIGSEGV vendetta.
The dialog only seems to pop under 32bit distros. It never did with the 64 or 32bit client under 64bit distros.

Distros used were 32 and 64bit versions of Archlinux, Ubuntu 9.04 and 9.10.

Here's a backtrace of the game under 64bit Archlinux.

#0 0x00000000005a6288 in ?? ()
#1 0x00000000005a63d5 in sigsegv_trap ()
#2 <signal handler called>
#3 0x00007ffff6a3c707 in ioctl () from /lib/libc.so.6
#4 0x00007ffff49a62d4 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#5 0x00007ffff49a3e93 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#6 0x00007ffff49fac17 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#7 0x00007ffff49f88c5 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#8 0x00007ffff484832a in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#9 0x00007ffff47d6657 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#10 0x00007ffff4842045 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#11 0x00007ffff47884ac in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#12 0x00007ffff47dfe15 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#13 0x00007ffff47de7f1 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#14 0x00007ffff3f60aeb in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#15 0x00007ffff3f619cf in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#16 0x00007ffff4008c05 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#17 0x00007ffff4006bdf in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#18 0x00007ffff3936a5f in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#19 0x00007ffff394362f in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#20 0x00007ffff3943b4c in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#21 0x00007ffff5d1b5e6 in OpenGLRef::RenderPrimitive2(OGLVB*, OGLIB*, GKPrimitive*) () from /home/ich/.vendetta/drivers/gkgl.so
#22 0x000000000057d190 in ?? ()
#23 0x000000000057d7ff in ?? ()
#24 0x000000000057d9e5 in ?? ()
#25 0x000000000057dd0c in ?? ()
#26 0x0000000000429fb6 in ?? ()
#27 0x000000000042a0f5 in ?? ()
#28 0x000000000042a825 in ?? ()
#29 0x00000000004318db in ?? ()
#30 0x00007ffff69969ed in __libc_start_main () from /lib/libc.so.6
#31 0x0000000000419cb9 in ?? ()
#32 0x00007fffffffe528 in ?? ()
#33 0x000000000000001c in ?? ()
#34 0x0000000000000001 in ?? ()
#35 0x00007fffffffe8a1 in ?? ()
#36 0x0000000000000000 in ?? ()

Looks like it's segfaulting a second time in the signal handler.