Program received signal SIGSEGV, Segmentation fault. 0x002a9582 in ?? () (gdb) BT #0 0x002a9582 in ?? () #1 0x009d5c44 in ?? () #2 0x00000106 in ?? () #3 0x009a6aa6 in ?? () #4 0x005e3940 in ?? () #5 0x09f72cf4 in ?? () (gdb)
Doesn't look like a better output than without debugging option... I never did this before. Is something missing?
It looks like the programm is jumping to some location with doesn't contain any real code. This is normaly a result of a memory corruption that is happeing earlier and very hard to track down.
There is an easy way to work around it. Run the program under gdb and it'll remember the trace even the memory (frames) gets corrupted.
gdb /path/to/httpd gdb> run -X issue a request here and gdb will tell you that you've got a segfault <gdb> bt will give you the trace.
Alex, I'd too suggest that you try to eliminate embperl and see if you can get the same problem with a plain mod_perl script/handler just like Gerald has suggested.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
