ID: 36472
Updated by: [EMAIL PROTECTED]
Reported By: Eskil dot Swahn at LDC dot lu dot se
-Status: Open
+Status: Feedback
Bug Type: Apache related
Operating System: Tru64 UNIX V5.1B
PHP Version: 4.4.2
Previous Comments:
------------------------------------------------------------------------
[2006-02-21 15:07:02] Eskil dot Swahn at LDC dot lu dot se
Something that was interesting as well was that 'httpd -X' doesn't
coredump, it's not until I run 'apachectl startssl' that I trigger the
memory fault..
------------------------------------------------------------------------
[2006-02-21 15:05:52] Eskil dot Swahn at LDC dot lu dot se
I have generated a core file and I am waiting on help from HP on how to
handle the debugger. My session so far:
dbx version 5.1
Type 'help' for help.
Core file created by program "httpd"
thread 0x4 signal Segmentation fault at >*[strcmp, 0x3ff800d8334]
ldq_u t1, 0(a1)
(dbx) help
Command syntax: "help <keyword>", <keyword> is one of the following
list:
most_used, quit, alias, record, playback, history, lineedit, run,
rerun, stop, step, next, trace, delete, catch, ignore,
cont, return, when, goto, print, printx, printo, printd,
printf, printregs, where, status, whatis, which, whereis, assign,
tag, up, down, func, dump, display, list, search,
edit, file, use, set, setenv, sh, stopi, conti,
stepi, nexti, tracei, listobj, enable, disable, kernel, tlist,
tset, tstack, call, attach, detach, plist, switch, variable,
register, builtin, expression
(dbx) trace
trace
^ syntax error
(dbx) help trace
trace <exp> - print <exp> when it changes
trace <exp> at <line> - print <exp> when <line> is reached
trace <exp> in <proc> - print <exp> when call <proc>
trace <exp> at <line> if <exp> - print <exp> when <line> is reached and
<exp>
trace <exp> in <proc> if <exp> - print <exp> when call <proc> and
<exp>
(dbx) quit
Does this help in any way so far?
------------------------------------------------------------------------
[2006-02-21 11:17:43] [EMAIL PROTECTED]
No, you're on your own for that... but your best bet would be to start
apache in single process mode (-X) in the debugger and then request
your script. The debugging should capture it when it segfaults and i
guess there is a command to make a backtrace then.
------------------------------------------------------------------------
[2006-02-21 11:12:28] Eskil dot Swahn at LDC dot lu dot se
Checked the instructions for generating a backtrace.
Any chance of instructions for T64's dbx instead of gdb?
------------------------------------------------------------------------
[2006-02-21 10:51:03] [EMAIL PROTECTED]
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/36472
--
Edit this bug report at http://bugs.php.net/?id=36472&edit=1
