[xdebug-general] Re: Xdebug, Komodo, and Apache 2.2.3

Hello Derick,

Thanks for the reply. Do you keep a dll of the latest cvs version
somewhere on your
site? I'll turn on the remote logging and try it again.

I don't know if I can come up with a short script to reproduce the
problem but I'll try.

But on a related note, I also get a similar apache memory error when I
expand the tree
view (click on the '+') for a multi-dimensional array to see its values
within the debug panel
in Komodo. This doesn't happen with every multi-dim array. But when it
does happen
with one particular multi-dim array, it happens all the time. Does
komodo fetch values
for arrays from Xdebug as it needs them?

Alex

Derick Rethans wrote:
> Hello Alex,
>
> On Tue, 19 Dec 2006, Alex wrote:
>
>
>> I'm using Windows XP, komodo 3.5.3 and 4 b3, Apache 2.2.3, PHP 5.2,
>> Xdebug 2.0 rc2.
>>
>> There have been a few times that I'll be stepping through code about 4
>> or 5 files deep. Then the Apache process will exit with the following
>> in the log: Parent: child process exited with status 3221225477 --
>> Restarting. I also get a message from Windows XP indicating a memory
>> error. It doesn't matter whether I step into or step through the code
>> that I think is causing the problem, apache still exits.
>>
>> What I would like to know is if there is anything that I can do to
>> find the possible cause of these apache memory errors. Could it be
>> that Komodo is causing this?
>>
>
> What would help for me to find is is a short reproducable script, the
> "remote log" (you can turn that on with the xdebug.remote_log=c:\foo.log
> php.ini setting) and a few steps to reproduce the problem. I did address
> a few problems in the latest CVS version and you might have had a
> slightly outdated version as the pecl2win machine has been stalled for
> some time. I do not think that Komodo can cause those errors.
>
> regards,
> Derick
>
>
Received on Tue Dec 19 2006 - 16:03:33 GMT