Closed GoogleCodeExporter closed 9 years ago
That's not a segfault. Can you get me a stack trace? I don't
have any such issues.
Can I assume that nm-applet has something to do with
NetworkManager (people actually use that?)?
Original comment by maglion...@gmail.com
on 20 Oct 2011 at 8:33
What do I have to tweak to include debugging symbols?
Otherwise the binary is stripped (I guess).
Original comment by d8ot0...@gmail.com
on 20 Oct 2011 at 8:52
The default build configuration includes debugging symbols. If
you're building a .deb, there's some debuild magic to get it not
to strip, but it's best to just do an ordinary build and either
install it to a temporary tree or just run the binary from the
build tree.
Or you could install it normally and run 'make uninstall' when
you're done.
Original comment by maglion...@gmail.com
on 20 Oct 2011 at 9:00
Thanks for info (I've always been using deb target):
Reading symbols from /home/kraay/wmii-hg-new/wmii/cmd/tray/witray.out...done.
(gdb) run
Starting program: /home/kraay/wmii-hg-new/wmii/cmd/tray/witray.out
client_manage(0x1600003): Caught error.
Program received signal SIGSEGV, Segmentation fault.
0x08052a6d in cleanupwindow (w=0x0) at x11/windows/destroywindow.c:8
8 assert(w->type == WWindow);
(gdb) bt
#0 0x08052a6d in cleanupwindow (w=0x0) at x11/windows/destroywindow.c:8
#1 0x08052b3b in destroywindow (w=0x0) at x11/windows/destroywindow.c:22
#2 0x0804a2b8 in client_cleanup (e=0x8086158) at client.c:65
#3 0x0804d65e in xembed_disown (xembed=0x8086158) at xembed.c:64
#4 0x0804a163 in client_manage (w=23068675) at client.c:32
#5 0x0804aa92 in message (s=0x808cd90, ev=0xbffff44c) at main.c:94
#6 0x0804b74f in message_event (w=0x808cec8, aux=0x808cd90, ev=0xbffff44c) at
selection.c:164
#7 0x0804dbb1 in _event_handle (w=0x808cec8, offset=60, event=0xbffff44c) at
event/event.c:43
#8 0x0805386f in event_clientmessage (ev=0xbffff44c) at
event/clientmessage.c:11
#9 0x0804dc5b in event_dispatch (e=0xbffff44c) at event/event.c:59
#10 0x0804dc9f in event_check () at event/event.c:70
#11 0x0804dfd0 in event_fdready (c=0x807ac18) at event/ixp.c:17
#12 0x0805bd0e in handle_conns ()
#13 0x0805be41 in ixp_serverloop ()
#14 0x0804b10b in main (argc=0, argv=0xbffff648) at main.c:207
Original comment by d8ot0...@gmail.com
on 20 Oct 2011 at 9:20
This issue was closed by revision 030637afd813.
Original comment by maglion...@gmail.com
on 20 Oct 2011 at 9:29
That's interesting. There's some other issue at play. Some X
error is occurring when we're trying to swallow the window,
though I can't imagine what it might be.
Original comment by maglion...@gmail.com
on 20 Oct 2011 at 9:30
Confirmed -- problem solved. Thanks!
Original comment by d8ot0...@gmail.com
on 20 Oct 2011 at 9:51
Original issue reported on code.google.com by
d8ot0...@gmail.com
on 20 Oct 2011 at 8:28