ID: 38775
User updated by: iain at iaindooley dot com
Reported By: iain at iaindooley dot com
-Status: Feedback
+Status: Open
Bug Type: Scripting Engine problem
Operating System: FreeBSD 6.1
PHP Version: 5.1.6
New Comment:
okay, in my configure line i have --enable-debug. on the page with
instructions to obtaining a backtrace, it says i need to compile
--with-debug. will compiling with --with-debug instead of
--enable-debug improve the backtrace?
Previous Comments:
------------------------------------------------------------------------
[2006-09-11 08:17:05] [EMAIL PROTECTED]
>is this something incorrect i have done in my php script?
> i don't know what ap_getline is.
No, it's not about you or your script.
ap_getline() is a function from Apache API, so it just can't appear in
CLI.
------------------------------------------------------------------------
[2006-09-11 08:16:51] [EMAIL PROTECTED]
Because ap_getline() really looks like an Apache httpd internal
function.
Anyway, you can produce much better backtraces with a debug build.
Thanks.
------------------------------------------------------------------------
[2006-09-11 08:03:29] iain at iaindooley dot com
okay, i'll put a script into cron that doesn't do much and see if it
segfaults.
i'm a bit mystified by the last line of the comment:
"ap_getline () in CLI? Something is really broken there."
is this something incorrect i have done in my php script? i don't know
what ap_getline is.
the scripts that are producing this problem are largish applications.
based on the information available do you have any suggested content
for a script to test on the command line?
------------------------------------------------------------------------
[2006-09-11 07:36:48] [EMAIL PROTECTED]
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
ap_getline () in CLI? Something is really broken there.
------------------------------------------------------------------------
[2006-09-11 06:46:07] iain at iaindooley dot com
i followed the instructions on obtaining a backtrace, however the
backtrace i received does not seem to be as helpful as the example:
---Type <return> to continue, or q <return> to quit---
#385 0x00000001 in ?? ()
#386 0x283303d8 in ?? ()
#387 0x28317cdd in ?? ()
#388 0x08066bc4 in ap_getline ()
the previous lines (of which there are many) are all similar to the
three above ap_getline, ie. they all have an address and ?? ()
i checked my config, and i ran ./configure with --enable-debug. i
notice on the page with instructions to obtain a backtrace it is
--with-debug. is there a difference?
a different application on the same machine that also runs scripts on
the command line had this backtrace:
#2464 0x0000008c in ?? ()
#2465 0x0838c950 in ?? ()
#2466 0x00000000 in ?? ()
#2467 0x28316cdd in ?? ()
#2468 0x08064280 in ap_cfg_getline ()
Previous frame inner to this frame (corrupt stack?)
once again i have ommitted many lines above that were ??()
------------------------------------------------------------------------
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/38775
--
Edit this bug report at http://bugs.php.net/?id=38775&edit=1
