>Joshua meant for you to run it in gdb with that option, but it might not
>be very helpfull if you didn't compile with CFLAGS=-g
Well, I did PERL_DEBUG=1, which allegedly does that. :)
>But you can try it anyay:
>
>gdb ../bin/httpd
>
>(gdb) run -X
><likely to give a segmentation fault>
>(gdb) bt
>
>and send the information it gives here.
(gdb) run -X -f conf/httpd.conf.mod_perl
Starting program: /web1.3/conf/../bin/httpd -X -f conf/httpd.conf.mod_perl
Program received signal SIGSEGV, Segmentation fault.
0x80de49c in Perl_gv_fetchpv ()
(gdb) bt
#0 0x80de49c in Perl_gv_fetchpv ()
#1 0x80da33f in Perl_get_sv ()
#2 0x808a461 in perl_create_request_config ()
#3 0x808a6ac in perl_cmd_handler_handlers ()
#4 0x80afde6 in ap_clear_module_list ()
#5 0x80b0223 in ap_handle_command ()
#6 0x80b02b7 in ap_srm_command_loop ()
#7 0x80b0910 in ap_process_resource_config ()
#8 0x80b1182 in ap_read_config ()
#9 0x80bb0a9 in main ()
#10 0x400df1eb in __libc_start_main (main=0x80bae1c <main>, argc=4,
argv=0xbffffc54, init=0x8062748 <_init>, fini=0x816442c <_fini>,
rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffffc4c)
at ../sysdeps/generic/libc-start.c:90
> > Pretend like I'm NOT some C-code guru, and explain to me what I need
>> to do, because it doesn't seem like doing what the docs say is
>> helping. *chuckle*
>
>Isn't there anything about debugging in the documentation?
It all seems centered around, near as I can tell, "debugging a server
that runs but takes a dump on a particular script/URL/etc."
D
--
+---------------------+-----------------------------------------+
| [EMAIL PROTECTED] | "Thou art the ruins of the noblest man |
| Derek J. Balling | That ever lived in the tide of times. |
| | Woe to the hand that shed this costly |
| | blood" - Julius Caesar Act 3, Scene 1 |
+---------------------+-----------------------------------------+
