[xdebug-general] Re: testing a remote install

Hi Mike.

Can you share what version of Notepad++ and dbgpPlugin.dll are you using?
(About dialog)
How do you have you mappings set up? Perhaps there is a problem with the
SOURCE command.
Please look at the file that is opened by Notepad++. Does it have "strange"
characters, like %?
The PHP crash may be connected to some bad path or similar. SOURCE on
windows was poorly tested as I don't have a setup like that.
I can quite imagine where the other Notepad++ crash comes from. Will be
fixed.

Best regards,
-Zobo

----- Original Message -----
From: "Mike D'Ambrogia" <miked[@]jamagination.com>
To: <xdebug-general[@]lists.xdebug.org>
Sent: Tuesday, October 23, 2007 6:17 PM
Subject: [xdebug-general] Re: testing a remote install

>> You don't configure the client (the "debugclient" is actually the
> "server" :)
>
> That one took me a few seconds to figure out, had to read the
> description 2x to figure out that xdebug.remote_host is really setting
> gui_client_address
>
> Think my problem might be firewall oriented now, so I'm off to
> confirm/deny that traffic is coming thru port 9000 because my
> debugclient never wakes up on remote traffic but does come alive for
> debugging calls off of my local webserver.
>
> As a side note, I found the debugclient-0.9.0 for linux download but it
> does not run on my box, chmod to 744 and get a "-bash:
> ./debugclient-0.9.0: cannot execute binary file". I can't compile from
> source since my sys op who does that is on vacation till next week - any
> other suggestions for a linux command line debugging client?
>
> And finally when I'm running debugging clients (notepad++) for local
> debugging sessions I load a browser, pass the XDEBUG_SESSION_START=mike
> on the page, control passes to the debugging client and source loads in
> the client window, but after a 'step into' I get an error "php.exe has
> generated errors and will be closed by Windows. You will need to
> restart the program." hitting ok clears the dialog and immediately I get
> an other dialog message of "Asynchronous socket error 10053" - hitting
> F7 to step in causes the app to "generate errors and will be closed by
> windows. You will need to restart the program". Dr Watson shows a
> "Exception number: c0000005 (access violation)". Any ideas where to dig
> in on PHP 4.4.7 to see why it's crashing like this? Going to try a few
> of the other clients to see if the error happens there as well.
>
> Thx
>
> Mike
>
>
>
Received on Tue Oct 23 2007 - 22:03:48 BST