On Fri, 9 Jun 2000 10:28:14 -0700 (PDT), Doug MacEachern wrote:
>try this:
>(gdb) source mod_perl-x.xx/.gdbinit
>(gdb) curinfo
>
>hopefully that will print the filename:line of the code Perl was running
>here. maybe that will shed some light.
(gdb) set args -X
(gdb) run
Starting program: /usr/sbin/httpd -X
Program received signal SIGSEGV, Segmentation fault.
0x401e2758 in net_write_command () from /usr/lib/apache/mod_auth_mysql.so
(gdb) bt
#0 0x401e2758 in net_write_command () from /usr/lib/apache/mod_auth_mysql.so
#1 0x40341238 in ?? () from /usr/lib/apache/mod_perl.so
#2 0x78756e69 in ?? ()
Cannot access memory at address 0x6c2e6264
(gdb) source /usr/src/redhat/BUILD/mod_perl-1.24/.gdbinit
(gdb) curinfo
Attempt to extract a component of a value that is not a structure pointer.
(gdb) bt
#0 0x401e2758 in net_write_command () from /usr/lib/apache/mod_auth_mysql.so
#1 0x40341238 in ?? () from /usr/lib/apache/mod_perl.so
#2 0x78756e69 in ?? ()
Cannot access memory at address 0x6c2e6264
(gdb)
There is no "net_write_command" call within the mod_auth_mysql code or object
based on the output of 'strings' and 'grep'.
>do you have these same troubles if mod_perl is linked static?
I don't know. Building it statically is not a process I'm familiar with. I've
been trying to start from a known point -- mod_auth.c and cut back in the code
for various mod_auth_mysql functions. I've got a version of mod_auth_mysql.c
that if I compile in 1 more function, it dies in mod_perl.so when I access a
mod_perl handled script. I've messed with structure variables, etc by
including and excluding items and it comes back to the same thing, touch a
mod_perl script with too much code in mod_auth_mysql (or even mod_example which
I was screwing around with) and *BOOM* the server seg faults.
Any help would be greatly appreciated.
Michael
