> > I can reproduce gdb crashes like this (attaching to a running X11 program,
> > apparently that is used by bug-buddy):
> >
> > % /usr/openwin/bin/xterm &
> > [1] 20797
> >
> > % /bin/gdb /usr/openwin/bin/xterm 20797
> > ...
> > Reading symbols from /usr/openwin/lib/libXt.so.4...done.
> > Loaded symbols for /usr/openwin/lib/libXt.so.4
> > Reading symbols from /usr/openwin/lib/libX11.so...Segmentation fault (core
> > dumped)
>
> I'm having the exact same issues, and am considering
> downgrading to b84 if I can't discover a workaround.
For the gdb segfault issue when the debug target
is using snv_85's libX11.so a workaround is to strip
the dwarf debug symbols from file /usr/X11/lib/libX11.so.4,
using strip -x (but don't do it while you're logged into X11 :-).
snv_85 / 86 accidentally delivered an unstripped libX11.so.4:
http://www.opensolaris.org/jive/thread.jspa?threadID=56481&tstart=0#222423
Otherwise, the gam_server process has crashed a couple of times
in the last couple of days, apparently with some kind of "assertion failed":
# mdb - /cores/gam_server-1044
Loading modules: [ libc.so.1 ld.so.1 ]
> $c
libc.so.1`_lwp_kill+7(16, 6)
libc.so.1`raise+0x22(6)
libc.so.1`abort+0xcd(80c156c, 80c1508, fee48088, 80669d5, 8089310, c)
libglib-2.0.so.0.1400.4`g_logv+0x340(0, 4, 806ffe4, fd8d1ebc)
libglib-2.0.so.0.1400.4`g_log+0x25(0, 4, 806ffe4, 807002c, ea)
events_unsafe_emit+0x100(80c1508, 10, 80a8100)
events_process_task+0x10b(8089e58)
thread_run+0x7b(8085ea8)
libc.so.1`_thr_setup+0x70(febca200)
libc.so.1`_lwp_start(febca200, 0, 0, 0, 0, 0)
> 806ffe4/S
0x806ffe4: file %s: line %d: should not be reached
> 807002c/S
0x807002c: gam_fen.c
> ea=D
234
So it seems gam_server tries to report:
file gam_fen.c: line 234: should not be reached
After gam_server has crashed, I have to use the workaround
from bug 6682362 to unblock JDS:
rm /tmp/fam-$USER/fam-
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6682362
This message posted from opensolaris.org
