[news.eclipse.tools.pdt] Re: How to prevent debug opening the browser?

[tanzanite7@xxxxxxxxx (Hell No)]

> As to why PDT is working the way it is for the non-JIT debug setup... 
> Xdebug looks for a cookie within the current page request to see if it 
> should send debug information to the remote host. The only way for that 
> cookie to exist is for PDT to open up a browser with the cookie 
> information put into the URL so that Xdebug can set the cookie. Check 
> out: http://www.xdebug.org/docs/remote and look at the section on HTTP 
> Debug Sessions. PDT is doing its bests to handle what Xdebug requires to 
> get a debug session started.

That, as far as i can see, is incorrect. I use FF extension XDebug helper 
for that. ie i tell trough FF when and where i want to debug - and it 
works just fine. It's just the hassle with the bound-to-be-useless initial 
debug session spawn (that i exit / ignore / close anyway) that i would 
like to be without.

Do not know eclipse inner logic related to that, so can't really know how 
or whether this can be done. Logically, there should be no problems (ie 
current project + current debug config [just the config] + xdebug 
connection spawned by whatever means [FF extension in this case] should be 
enough).

One thing i am wondering: eclipse spawn has &KEY=<some number that looks 
like time> attached. Does not show up in xdebug communication (visibly) 
nor in xdebug documentation. What is it?