Thats the output I got:
Program received signal SIGSEGV, Segmentation fault. 0x006bc582 in ?? () (gdb) (gdb) (gdb) BT #0 0x006bc582 in ?? () #1 0x00603c44 in ?? () #2 0x00000106 in ?? () #3 0x005d4aa6 in ?? () #4 0x010a6940 in ?? () #5 0x0ab5c5bc in ?? () #6 0x41414141 in ?? () #7 0xbfe6e9a8 in ?? () #8 0x00fdebdd in ?? () #9 0x41414141 in ?? () #10 0x0a8be838 in ?? () #11 0x006039e4 in ?? () #12 0x0ab5c5bc in ?? () #13 0x0aa8d29c in ?? () #14 0xbfe6e9c8 in ?? () #15 0x005e2493 in ?? () #16 0x0ab5c5bc in ?? () #17 0x004c1410 in ?? () #18 0x0a8be838 in ?? () Is THIS really useful? Should I compile with debugging symbols? If yes what? apache or mod_perl? or embperl? Thanks, Alex Von: Gerald Richter <[EMAIL PROTECTED]> am 12.11.2003 07:55 An: Alexander Hartmaier/DEBIS/EDVG/[EMAIL PROTECTED], [EMAIL PROTECTED] Kopie: [EMAIL PROTECTED] Thema: Re: [mp2] segfault when generating graphs with GD::Graph under Embperl > > 3. This is the core dump trace: (if you get a core dump): > > I tried but I can't catch any (I don't know and didn't manage to find out which > directory has to be writeable for the apache2 process under Embperl). > Please try to start your httpd under gdb: gdb /path/to/httpd set args -X -f /path/to/httpd.conf r Now request the page that segfaults, gdb should show the segfault, then type BT and you should get the backtrace. Gerald P.S. -X tell Apache to only start one process, which is better for debugging *2* -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
