[xdebug-general] Re: Eclipse is stuck at Waiting for Xdebug session... progress at 48%

On 1/19/17 9:17 AM, jack birr wrote:
>
> I found some solutions:
>
> 1) I set xdebug.remote_autostart=on in the php.ini and this caused a
> debug session in Eclipse to start when the client side POSTed to a
> PHP file. That is behavior that I was unsure if or how it might
> work. So learning about the xdebug.remote_autostart option will be
> useful
>
> 2) I create a new eclipse debug configuration and start an Eclipse
> debug session with a PHP file as the starting point. This is the how I
> used the debugger in the past with Joomla and I should tried this sooner.
>
> When I finally started a session I did create a xdebug log file.
>
> I set up all of the software with the latest downloads of everything.
> So my problem was not any specific version of software.
>
> When Eclipse is waiting at 48% in my environment there will never be a
> connection. Other posters got stuck waiting at 57% progress. I am
> not sure what is not responding. But altering the debug configuration
> was the solution.
>
> Hope this helps someone else.
>
>
> On 1/13/2017 1:24 PM, jack birr wrote:
>> Debugging with Eclipse and Xdebug does not appear to be working.
>> Breakpoints do not break; code just runs without breaking. I have
>> read of this problem in other forum posts but there is no solution
>> that works for me.
>>
>> Here is what happens:
>> I launch an Eclipse Debug Configuration to start debugging.
>> Eclipse loads the starting file (which is HTML only in this case) in
>> Firefox with the Xdebug parameter:
>> ?XDEBUG_SESSION_START=ECLIPSE_DBGP&KEY=14840873439273
>> Eclipse shows Launching: Waiting for Xdebug session... progress shows 48%
>> When I terminate the debugging session in Eclipse another copy of my
>> starting file is loaded in Firefox with another Xdebug parameter:
>> ?XDEBUG_SESSION_STOP_NO_EXEC=ECLIPSE_DBGP&KEY=14840873439273
>> There does not seem to be a connection between Eclipse and Xdebug
>>
>> I have checked everything I can think of.
>> netstat shows:
>> TCP 0.0.0.0:9000 computer:0 LISTENING
>> [eclipse.exe]
>>
>> I added the a log name to Xdebug but none of my attempts created any
>> log file and certainly not any entries in a log file.
>>
>> I have focused on Xdebug as the problem because of other posts about
>> Eclipse Waiting on Xdebug 48% messages.
>> I tried Xdebug 2.4.1 but the results were the same: Waiting at 48%
>>
>> Does anybody have any ideas what I should do?
>>
>>
>> More details about my setup:
>>
>> I'm on Windows 10 64-bit
>> I had set up Eclipse and Xdebug previously on a Windows 7 machine
>> I was rebuilding my environment and downloaded:
>> XAMPP Version 5.6.28
>> Eclipse Neon.2 Release (4.6.2) (64-bit)
>> Java runtime 8 111 (64-bit)
>> Xdebug 2.5.0 (|php_xdebug-2.5.0-5.6-vc11.dll|)
>>
>> Xdebug install Summary:
>> Xdebug installed: 2.5.0
>> Server API: Apache 2.0 Handler
>> Windows: yes - Compiler: MS VC11 - Architecture: x86
>> Zend Server: no
>> PHP Version: 5.6.28
>> Zend API nr: 220131226
>> PHP API nr: 20131226
>> Debug Build: no
>> Thread Safe Build: yes
>> Configuration File Path: x:\window
>> Configuration File: x:\xamp\php\php.ini
>> Extensions directory: x:\xamp\php\ext
>>
>> My additions to php.ini are:
>> zend_extension=x:\xamp\php\ext\php_xdebug-2.5.0-5.6-vc11.dll
>> xdebug.profiler_output_dir="x:\xamp\tmp"
>> xdebug.remote_enable=on
>> xdebug.remote_log="x:\xamp\tmp\xdebug.log"
>> xdebug.trace_output_dir="x:\xamp\tmp"
>>
>> These php.ini updates are confirmed in phpinfo(). The file paths
>> have been changed for public consumption.
>>
>
Acknowledging that one's natural and certainly unsinful inclination is
to top post, I nevertheless apologize for making you scroll down here.

Ah, I see... Yes, what you experienced is due to how it looks like you
are working with one of those awful projects that internally sends a
POST request to code that it should be calling normally since it's
already part of the code, leaving one confounded by normal
configurations of Xdebug as you most certainly had setup, causing you to
scour the Internet for that darn autostart. You can alternately add the
Xdebug request parameter to the internal POST request if possible.

Don't get me wrong: sometimes you'd want your PHP application to curl
some part of itself that a client would for some specific part of the
app for some decent reason, but that is not how a web app should
generally operate. Sorry I didn't take note of your plight earlier, but
I'm glad you got it sorted out.

-- 
-Spencer <http://aninternetpresence.net>
-----------------
"What a lark! What a plunge!"
- Mrs. Dalloway <http://ebooks.adelaide.edu.au/w/woolf/virginia/w91md/>, 
Virginia Woolf