> And how do you look at contents of coredump?

$ gdb /path/to/httpd core.file

Once inside gdb you can use bt and bt full to get the stacks. You can
use print to get the contents of a variable.

> ===========
> Program terminated with signal 11, Segmentation fault.
> #0  0x00002b99fabc6aa2 in apr_socket_addr_get () from /usr/lib/libapr-1.so.0
> ===========

That looks like the seg fault that is caused when sock is null.  A
check for null could be put in.  From Lazy's earlier email:

>> everything happens just after graceful
>>
>> Program terminated with signal 11, Segmentation fault.
>> #0  apr_socket_addr_get (sa=0x8315014, which=APR_LOCAL, sock=0x0) at
>> sockaddr.c:196
>> 196             if (sock->local_interface_unknown ||
sock->local_port_unknown) {
>> (gdb) bt full
>> #0  apr_socket_addr_get (sa=0x8315014, which=APR_LOCAL, sock=0x0) at
>> sockaddr.c:196
>> No locals.
>> #1  0x080b74ec in core_create_conn (ptrans=0x8314fc8,
>> server=0x80ef1f0, csd=0x0, id=263, sbh=0x8315000, alloc=0x8316fd0) at
>> core.c:4477
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser

Reply via email to