Hi,
I forgot to mention that I am building 0.95.5 on NetBSD x86, that's
the latest package there.
On 2014-07-04 10:51:11 +0200 a...@zencoding.org wrote:
Not sure if anyone is running NetBSD here though. I think I have a
NetBSD VM
around, but I'm moving this weekend and the computer it's on is in a
big box
right now. I'll try to see how I can reproduce this some time next
week-ish,
but I'm likely going to be stuck without Internet for a week or two.
Sadly,
wManageWindow is about 600 lines so I can't offer any useful
inference as to
what borks.
when compiling with -O0, everything works. When compiling with -O2, I
am now able to get this stacktrace:
#0 fixLeaderProperties (wwin=0x0) at window.c:465
#1 wManageWindow (scr=scr@entry=0xbb442000,
window=window@entry=10485773)
at window.c:737
#2 0x0806eac0 in handleMapRequest (ev=0xbfbfe8a8, ev=0xbfbfe8a8)
at event.c:621
#3 DispatchEvent (event=0xbfbfe8a8) at event.c:229
#4 0xbbbad544 in WMHandleEvent (event=event@entry=0xbfbfe8a8) at
wevent.c:208
#5 0x0806ffa5 in EventLoop () at event.c:402
#6 0x080a4bac in real_main (argv=0xbfbfe988, argc=<optimized out>)
at main.c:849
#7 main (argc=2, argv=0xbfbfe988) at main.c:649
I suppose that for some reason wwin is null?
(gdb) p wwin
$1 = (WWindow *) 0x0
(gdb) p window
$2 = 10485773
(gdb) p title
$3 = 0xbb152500 "xterm"
I hope this helps a little more.
Riccardo
--
To unsubscribe, send mail to wmaker-user-unsubscr...@lists.windowmaker.org.
