MantisBT - Xdebug
View Issue Details
0000198Xdebug(No Category)public2006-09-05 07:592006-09-07 22:57
tylerj 
 
normalcrashalways
closedopen 
 
 
OSX Intel 10.4.7
5.1.4
0000198: Crash in xdebug.c:1298 (2.0.0beta6)
Segfault at xdebug.c:1298

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x0100d17a in xdebug_execute (op_array=0x252a61c, tsrm_ls=0x1101790) at /Users/tylerj/php-debug/xdebug-2.0.0beta6/xdebug.c:1298
1298 if (!XG(context).handler->remote_init(&(XG(context)), XDEBUG_REQ)) {

Backtrace.

#0 0x0100d17a in xdebug_execute (op_array=0x252a61c, tsrm_ls=0x1101790) at /Users/tylerj/php-debug/xdebug-2.0.0beta6/xdebug.c:1298
#1 0x014d5344 in zend_execute_scripts ()
0000002 0x014733cf in php_execute_script ()
0000003 0x0154f177 in php_handler ()
0000004 0x0001c62c in ap_run_handler (r=0x18ce650) at config.c:152
0000005 0x0001ca2f in ap_invoke_handler (r=0x18ce650) at config.c:364
0000006 0x0000c556 in ap_process_request (r=0x18ce650) at http_request.c:249
0000007 0x000067ed in ap_process_http_connection (c=0x18ca730) at http_core.c:253
0000008 0x00028d7a in ap_run_process_connection (c=0x18ca730) at connection.c:43
0000009 0x00029098 in ap_process_connection (c=0x18ca730, csd=0x18ca650) at connection.c:176
0000010 0x0001a6aa in child_main (child_num_arg=0) at prefork.c:610
0000011 0x0001a8f4 in make_child (s=0x1841d30, slot=0) at prefork.c:650
0000012 0x0001aa07 in startup_children (number_to_start=5) at prefork.c:722
0000013 0x0001b421 in ap_mpm_run (_pconf=0x1807218, plog=0x183d218, s=0x1841d30) at prefork.c:941
0000014 0x0002204e in main (argc=2, argv=0xbffff40c) at main.c:623
Running with php 5.1.4 and Apache/2.0.58, installed via fink (apt-get for mac).

Running as a zend_ts module. (note that i think my apache is prefork, but i don't know anything about how modphp/libphp works)

Fails with phpeclipse and the debugclient.

Checked to see if the cvs version changed anything near that line and it didn't.

Will try cvs version, just rusty with the whole automake/autoconf situtation, so a few pointers will help.

I can get any other information if needed.
No tags attached.
Issue History
2006-09-05 07:59tylerjNew Issue
2006-09-05 08:02tylerjNote Added: 0000451
2006-09-06 04:50tylerjNote Added: 0000452
2006-09-06 04:54tylerjNote Edited: 0000452
2006-09-06 04:55tylerjNote Edited: 0000452
2006-09-07 22:57derickStatusnew => closed
2006-09-07 22:57derickNote Added: 0000453
2016-07-31 13:35derickCategoryDebug client (console) => debugclient (debugging tool)
2016-07-31 13:35derickCategorydebugclient (debugging tool) => (No Category)

Notes
(0000451)
tylerj   
2006-09-05 08:02   
Sorry i didn't see the category selection.
(0000452)
tylerj   
2006-09-06 04:50   
(edited on: 2006-09-06 04:55)
Same bug occurs in the lastest cvs version.

0x0100d71a in xdebug_execute (op_array=0x2525c1c, tsrm_ls=0x1101790) at /Users/tylerj/php-debug/xdebug/xdebug.c:1288
1288 if (!XG(context).handler->remote_init(&(XG(context)), XDEBUG_REQ)) {

cvs status xdebug.c
=======================================
File: xdebug.c Status: Up-to-date

   Working revision: 1.337
   Repository revision: 1.337 /repository/xdebug/xdebug.c,v
   Sticky Tag: (none)
   Sticky Date: (none)
   Sticky Options: (none)

edited on: 2006-09-06 04:54

edited on: 2006-09-06 04:55
(0000453)
derick   
2006-09-07 22:57   
This is now fixed in CVS. However, this could only happen if you specified a non-existing handler with the xdebug.remote_handler setting. You should use "dbgp" there. The code will now give a warning if you pick an nonexisting one.