[MacPorts] #26078: Cannot debug with the latest php5-xdebug, php5 and apache2 ports
MacPorts
noreply at macports.org
Sat Aug 14 17:48:31 PDT 2010
#26078: Cannot debug with the latest php5-xdebug, php5 and apache2 ports
-----------------------------------------+----------------------------------
Reporter: daniel.gasparotto@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: xdebug php apache2 | Port: php5-xdebug
-----------------------------------------+----------------------------------
Changes (by ryandesign@…):
* priority: High => Normal
Old description:
> After updating ports to:[[BR]]
> PHP @5.3.3[[BR]]
> apache2 @2.2.15[[BR]]
> php5-xdebug @2.1.0
>
> when I run a php script with debugger on, it fails and apache throws this
> error:
>
> httpd(9082) malloc: *** error for object 0x10400000f: pointer being freed
> was not allocated[[BR]]
> *** set a breakpoint in malloc_error_break to debug[[BR]]
> [Sat Aug 14 15:16:32 2010] [notice] child pid 9082 exit signal Abort trap
> (6)
>
> (using MacOSX 10.6.4 and PHPStorm)
New description:
After updating ports to:[[BR]]
PHP @5.3.3[[BR]]
apache2 @2.2.15[[BR]]
php5-xdebug @2.1.0
when I run a php script with debugger on, it fails and apache throws this
error:
{{{
httpd(9082) malloc: *** error for object 0x10400000f: pointer being freed
was not allocated
*** set a breakpoint in malloc_error_break to debug
[Sat Aug 14 15:16:32 2010] [notice] child pid 9082 exit signal Abort trap
(6)
}}}
(using MacOSX 10.6.4 and PHPStorm)
--
Comment:
Ok. I'm afraid I don't know what to do about this. You may want to
[http://www.xdebug.org/support.php speak with the developers of xdebug].
If they say we need to change something about the way we're packaging
xdebug in MacPorts, let us know.
--
Ticket URL: <http://trac.macports.org/ticket/26078#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list