[rt-devel] Segmentation Fault -- Help?
Benjamin D. Hudgens
benjamin at winternals.com
Thu Sep 4 13:33:31 EDT 2003
Hello --
Thank you for looking at this! Is this what you were looking for? I'm
not a heavy developer and unfamiliar with gdb mostly; thus, I'm not
exactly sure how to load the "debugging symbols".
bash-2.05b# gdb !$
gdb /usr/local/sbin/httpd
[...Snip...]
(gdb) set args -X
(gdb) run
Starting program: /usr/local/sbin/httpd -X
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x808c3bb in XS_Apache__Table_FETCH ()
(gdb) backtrace
#0 0x808c3bb in XS_Apache__Table_FETCH ()
#1 0x8119387 in Perl_pp_entersub ()
#2 0x81136b4 in Perl_runops_standard ()
#3 0x80d29ae in S_call_body ()
#4 0x80d2af2 in Perl_eval_sv ()
#5 0x80d2e5b in Perl_require_pv ()
#6 0x806fe06 in perl_reload_inc ()
#7 0x8064f5f in perl_restart ()
#8 0x806588f in perl_startup ()
#9 0x80655ef in perl_module_init ()
#10 0x80ad024 in ap_init_modules ()
#11 0x80b7a6e in standalone_main ()
#12 0x80b8378 in main ()
#13 0x8064a4e in _start ()
(gdb)
~Benjamin
-----Original Message-----
From: Robert Spier [mailto:rspier at pobox.com]
Sent: Thursday, September 04, 2003 12:17 PM
To: rt-devel at lists.fsck.com
Subject: Re: [rt-devel] Segmentation Fault -- Help?
Icky.
Can you reproduce this with httpd -X running under gdb and get a
proper backtrace?
-R
At Thu, 4 Sep 2003 11:24:46 -0500,
Benjamin D. Hudgens wrote:
>
> This will be long; but so has the process in which I've gone through
to
> resort to a post:
_______________________________________________
rt-devel mailing list
rt-devel at lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
More information about the Rt-devel
mailing list