Re: [RP] sparc segfault on startup with version 1.4.0

[Michael Graham]

> #0  0xff0b3218 in strlen () from /usr/lib/libc.so.1
> #1  0xff1065a0 in _doprnt () from /usr/lib/libc.so.1
> #2  0xff108470 in printf () from /usr/lib/libc.so.1
> #3  0x2a264 in get_wmname (w=279160) at manage.c:214
> #4  0x2a484 in update_window_name (win=0x56710) at manage.c:313
> #5  0x2a5c0 in update_window_information (win=0x56710) at manage.c:379
> #6  0x243d0 in listen_for_events () at events.c:989
> #7  0x2995c in main (argc=0, argv=0xffbeecfc) at main.c:688
> (gdb) quit
>
> Hi Michael,
>
> get_wmname has been rewritten since 1.4.0. Can you try building
> ratpoison out of CVS on your sparc machine? Hopefully the rewrite
> fixed this crash bug.

I've tried this with no success. But I have made some progress in
tracking down the bug. Solaris doesn't like printing null strings
printf("%s\n",NULL) will cause it to crash. Unfortunately finding all
of the places in ratpoison where this happens isn't going to be easy.

As I said in my original message it crashed randomly when I was using
the normal build and on startup with --enable-debug. This printf
problem certainly explains why --enable-debug causes it to crash
earlier but does it explain the original causes for crashing? Would
you code ever print without debuging on?

Thanks for your help

--
Michael Graham <address@hidden>