Ashok Nair wrote: > 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?
Ashok, what is the stack trace when you run $C or ::findstack (or pstack /path/to/core for that matter). That will give you a better idea of what happened. best regards, James C. McPherson -- Solaris Datapath Engineering Data Management Group Sun Microsystems
