-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
Since the following stack trace is only 32 frames large, I doubt this is an endless signal loop (something causes a signal, the signal handler causes the same signal again and so is called again, causes the signal again, ...) Since frame 0 is in some nvidia library, I blame nvidia. :/ Why is this library loaded at all? awesome doesn't do any opengl magic? Am 21.07.2010 12:31, Adam Nielsen wrote: > (gdb) bt > #0 0x00007f10b76b3940 in _nv000000gl () from > //usr/lib64/opengl/nvidia/lib/libnvidia-tls.so.1 > #1 0x00007f10ba8223d5 in ?? () from //usr/lib64/opengl/nvidia/lib/libGL.so.1 > #2 0x00007f10bfcc707c in _dl_fini () at dl-fini.c:248 > #3 0x00007f10bb689c65 in __run_exit_handlers (status=1, listp=0x7f10bb9a84a8, > run_list_atexit=true) at exit.c:78 > #4 0x00007f10bb689cb5 in *__GI_exit (status=-1164175704) at exit.c:100 It tries to exit but fails thanks to nvidia?! > #5 0x000000000043908b in _fatal (line=<value optimized out>, fct=<value > optimized out>, fmt=0x440775 "dumping backtrace\n%s") at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/common/util.c:44 > #6 0x00000000004103aa in signal_fatal (signum=<value optimized out>) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/awesome.c:260 > #7 <signal handler called> > #8 0x00007f10bb6c6f61 in mUSABLe (m=0xa2395f0) at malloc.c:5886 > #9 __malloc_usable_size (m=0xa2395f0) at malloc.c:4211 > #10 0x00007f10ba82155f in ?? () from //usr/lib64/opengl/nvidia/lib/libGL.so.1 > #11 0x00007f10b76b3a6b in ?? () from > //usr/lib64/opengl/nvidia/lib/libnvidia-tls.so.1 The above is again in libnvidia-tls, but luaA_client_gc() can't have called this...? > #12 0x0000000000411c2d in luaA_client_gc (L=0x1c2b920) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/client.c:55 client.c:55 is xcb_get_wm_protocols_reply_wipe(). I remember a bug with this one due to some ABI change in xcb-utils... :/ But this definitely should *not* call into any library from nvidia, wtf is going on? > #13 0x00007f10bc29e249 in luaD_precall (L=0x1c2b920, func=0x7f10b4189020, > nresults=0) at ldo.c:319 > #14 0x00007f10bc29e69d in luaD_call (L=0x1c2b920, func=0x7f10b4189020, > nResults=243713344) at ldo.c:376 > #15 0x00007f10bc29fbb4 in GCTM (L=0x1c2b920) at lgc.c:467 > #16 0x00007f10bc2a01af in luaC_callGCTM (L=0x1c2b920) at lgc.c:479 > #17 0x00007f10bc29de56 in luaD_rawrunprotected (L=<value optimized out>, > f=<value optimized out>, ud=<value optimized out>) at ldo.c:116 > #18 0x00007f10bc2a4699 in lua_close (L=0x1c2b920) at lstate.c:209 > #19 0x00000000004108c3 in awesome_atexit () at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/awesome.c:96 > #20 0x000000000041091d in awesome_restart () at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/awesome.c:276 > #21 0x0000000000425671 in luaA_panic (L=<value optimized out>) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/luaa.c:680 > #22 0x00007f10bc29e0cc in luaD_throw (L=0x1c2b920, errcode=2) at ldo.c:104 > #23 0x00007f10bc29a233 in lua_error (L=0xa2395f0) at lapi.c:967 > #24 0x00007f10bc2a9214 in luaL_error (L=0x1c2b920, fmt=0x7f10bc2b1f21 "stack > overflow (%s)") at lauxlib.c:93 The "old" stack overflow error is back. :( > #25 0x000000000043a14d in luaA_object_emit_signal (L=0x1c2b920, oud=<value > optimized out>, name=0x440d00 "property::icon", nargs=0) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/common/luaobject.c:234 > #26 0x000000000041d7e6 in property_update_wm_name (c=<value optimized out>, > reply=0xe9d8920) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/property.c:68 > #27 0x000000000041d8d8 in property_handle_wm_name (data=<value optimized out>, > connection=<value optimized out>, state=<value optimized out>, window=<value > optimized out>, name=<value optimized out>, reply=0xe9d8920) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/property.c:68 > #28 0x00007f10bd5c7c49 in call_handler (c=0x1c3d4f0, state=64 '@', > window=27440259, atom=39, h=0x1f66920) at property.c:63 > #29 0x0000000000410324 in a_xcb_check_cb (loop=<value optimized out>, w=<value > optimized out>, revents=<value optimized out>) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/awesome.c:223 > #30 0x00007f10bc4be6eb in ev_invoke_pending (loop=0x7f10bc6c7340) at ev.c:1971 > #31 0x00007f10bc4c2b0f in ev_loop (loop=0x7f10bc6c7340, flags=0) at ev.c:2333 > #32 0x00000000004112a7 in main (argc=<value optimized out>, argv=<value > optimized out>) at > /var/tmp/portage/x11-wm/awesome-3.4.4/work/awesome-3.4.4/awesome.c:572 Thanks for the stack trace, but I have no idea what is going on. All I can say is that awesome shouldn't be using any libraries from nvidia, any idea where they come from? Cheers, Uli - -- - - Buck, when, exactly, did you lose your mind? - - Three months ago. I woke up one morning married to a pineapple. An ugly pineapple... But I loved her! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBCAAGBQJMRtuDAAoJECLkKOvLj8sGm50IAI8dstX8sKvs0lzWnkvm2lWV w2g1wjj+b3OWYI0muHenbWbWBEpNKgzR14nlAvV1Cif7BPrcCAWcRAQw9k1AjNJp EILiy1vuZ8zMbpxIqSCLZS8rBuPhB+vRworSVzz48AbNnt90dvv/SXZt2lV+t/xt Pc44udw4KNWEzsQmBu2fs/FpVAVRSmhDAbJ3vQDFX0IQcKXh4MjwvpyZZJtdDO02 0IsDMwgOgr9CLD3zSplTFErqPMlIEIphvUJTyHGje7GfMOGvibHn5s+voIPi5r1/ 5D5V1twjCTGHaVXPFDYHnemDGnvd4wPzg0J7BZ3tG6AGiTQbkRZMzcf/mnxvLMY= =a8QG -----END PGP SIGNATURE----- -- To unsubscribe, send mail to [email protected].
