> > core file from an apache httpd process from Solaris 9 > > debugging core file of httpd (32-bit) from nonstop > executable file: /usr/local/bin/httpd > threading model: multi-threaded > status: process terminated by SIGSEGV (Segmentation Fault) > > <pc::dis -n 2 > libc.so.1`_read+4: mov 3, %g1 > libc.so.1`_read+8: ta 8 > libc.so.1`_read+0xc: bgeu +0x34 > <libc.so.1`_read+0x40> > libc.so.1`_read+0x10: cmp %o0, 0x5b > libc.so.1`_read+0x14: be,a -0x10 > <libc.so.1`_read+4> > > so did it core dump @ "libc.so.1`_read+0xc: bgeu +0x34 > <libc.so.1`_read+0x40>" ? > > What is the bad address in that instruction? Where to dig further?
Are you debugging the core file on the same machine where it was created or on a different machine? I ask because one possibility here is that if you are you're seeing the wrong text: prior to Solaris 10, text sections from executables and shared libraries were not included in core files and thus you can get mismatches if you are not careful about patch revisions, etc. If that isn't the issue, then let us know and I can explain how to look at the siginfo_t and see what is going on. -Mike -- Mike Shapiro, Solaris Kernel Development. blogs.sun.com/mws/
