How can I get the debugger out of auto-debug state? Usually the debugger won't run unless I use the "Debug" button on the debugger toolbar but I did something recently and now it debugs every request, including several requests per page for a favicon.ico! (which I've fixed by putting a favicon.ico there, but having that request load the debugger gave me a clue to what was happening.)

ALSO, is there any way to clear all pending debug requests (instead of having to click the stop button one at a time?)

FINALLY, is there any way to disable F5 from triggering the debugger while in the IDE w/o disabling the ability to use F5 to run the debugger after the debugger was triggered by the Debug button from the browser? It seems the functionality of "start a new debug session" and "continue running a debug session" are intertwined and thus it seems I'm unable to disable one without disabling the other...

if you turned on DebugSession (either in the IDE settings for the debugger or in the Debugger Toolbar menu), debugger will start for each request you run on the server. To stop DebugSession, you have to drop debugger cookie. It can be done with Run W/O Debugger, or by closing browser window (it works only with external browser and only if you close whole the window, not tabs).

You may want to turn DebugSession off.

Thanks for the reply. That is consistent with what I'm seeing as I am forced to use session in order to debug AJAX.

Unfortunately that means every time I refresh the page in order to refresh my Javascript it invokes the debugger for that page and I have to tab over to that page, step through that page that I don't want to debug, just to be able to get back to the point where I can debug my AJAX web service. It is rather distracting and can make it very difficult to concentrate when debugging complex code.

As for your alternate options, closing and then reopening the browser would be even more distracting, and I don't think you have a "run w/o debugger" option on the browser toolbar.

Is there any chance you can modify that behavior in future releases? For example, if you could add a flag to DBGSESSID that basically says "Debug just this one HTTP request and then turn off the debug session" it would make a huge difference.

Also, it would be nice to be able to define a set of rules for which files will be debugged and which will not be. That would allow us to streamline our debugging process quite a bit.

Thanks in advance for considering.

-Mike

What I said before related to DEBUG sessions, not PHP sessions. You are not "forced" to use DEBUG session
There are many posts related to debugging AJAX with dbg on this forum board, please don't hesitate to look for them.

Sorry for my wording, but can you address the question where I ask you to be able to specify to debug only one request in the DBGSESSID parameter? Or if that doesn't work, how about another parameter?



Well, I did that a while back and YOU told me what I needed was to use DBGSESSID. You didn't mention anything else and I wasn't able to find anything else on the topic at the time. For example, you answering someone else:



However, it was probably that I was having a hard time understanding how to debug AJAX at all. Just now I found DebugBreak() after about 15 minutes of searching. Is that what you refer to? (IF yes, why didn't you just say "Look for posts about "DebugBreak()" rather than being sarcastic and suggest I look for other posts as if I had never done that?) And are there other methods that you could tell me about to avoid sending me off on a potentially wild-goose chase?