On Sat, 6 Jun 2009 20:38:46 +0200 Julien Danjou <a...@debian.org> wrote:
> At 1244310678 time_t, hizel wrote: > > and with debug symbols > > Adding more info would be nice if you can (like the previous bt). > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0xb7822700 (LWP 7699)] > > 0x08054702 in client_seturgent () > > (gdb) bt > > #0 0x08054702 in client_seturgent () > > #1 0x0805f51a in property_update_wm_hints () > > #2 0x00000004 in ?? () > > #3 0x00000000 in ?? () > > (gdb) bt full > > #0 0x08054702 in client_seturgent () > > No symbol table info available. > > #1 0x0805f51a in property_update_wm_hints () > > No symbol table info available. > > #2 0x00000004 in ?? () > > No symbol table info available. > > #3 0x00000000 in ?? () > > No symbol table info available. > > > > :-\ > > Somehow, I don't buy it. That should be reproducible and so far no one > came with so many segfault doable by 2 differents way. :) > Something wrong on your system? Only awesome acts weird? > Only awesome. I reinstalled the debian and problem solved. Sorry. :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
