I'm starting to really like this debugger when using it with PHP. Much 
better than the old debugger.

I still see a problem with break points that exists in Komodo 2.5.2. And 
that is that break points set after the debugging starts sometimes (or 
all the time??) get ignored. Are break points to be set before the 
script starts?

I also noticed that "Run to Cursor" doesn't work (unless I'm doing 
something wrong). Can this feature be used after the script starts in 
the debugging session?

Also, is it possible to add a wild card option for the dumping of super 
globals settings... like so.

xdebug.dump.COOKIE = *
xdebug.dump.ENV = *
xdebug.dump.FILES = *
xdebug.dump.GET = *
xdebug.dump.POST = *
xdebug.dump.REQUEST = *
xdebug.dump.SERVER = *
xdebug.dump.SESSION = *


Alex


Derick Rethans wrote:

> On Wed, 30 Jun 2004, Alex Fernandez wrote:
> 
>   
> 
> >The help file with Komodo 3.0 Beta 4 states that we have to manually add
> >a GET var to the URL in order to trigger the remote debugger. Do we have
> >to do this when we're running the debugger locally on a local web
> >server? If so, then how are we supposed to debug pages which have forms?
> >Does this mean we have to edit the file to add the GET var to the form
> >action before being able to debug? We didn't have to do this with Komodo
> >2.5.2.
> >    
> >
> 
> You only need to do that for the first page, after that Xdebug tracks
> this for you (with a cookie). For more information on how Xdebug does
> this, see here:
> http://www.xdebug.org/docs-debugger.php#browser_session
> 
> regards,
> Derick
> _______________________________________________
> Komodo-beta mailing list
> Komodo-beta@[...].com
> http://listserv.ActiveState.com/mailman/listinfo/komodo-beta
> 
>   
>