[news.eclipse.tools.pdt] Re: problems with breakpoints in xdebug in PDT2

[Dave <dkel50@xxxxxxxxxxxxxxx>]

Hi Tom, sounds like you are using remote session initiation. 
Unfortunately currently there isn't any way to remember or configure 
that type of debug session. Maybe in a future release.

Dave Kelsey

Tom Walter wrote:
> Hi Dave,
>
> Thanks for pointing out the logging. I managed to figure out my problem.
>
> I have an auto-prepended bootstrap file that lives outside my php 
> project. Whenever I started a debug session it was asking me to choose a 
> file in my project to map to the bootstrap. Since there is no local 
> copy, I had copied it into my project root and point the xdebug plugin 
> at that. This seemed to work at first. But when I went to look in the 
> logs, I discovered the effect of this was to create a path mapping 
> between my project root and the server location of the bootstrap that 
> was being applied to all files. And of course this caused the breakpoint 
> mappings sent to xdebug to be completely incorrect.
>
> So I've removed that path mapping and now the breakpoints work as 
> expected. However it has an annoying side effect that whenever I start 
> the debug session it again asks me to map the bootstrap again. If I 
> choose 'Do not map' then the session works correctly, however that 
> setting does not seem to be stored.
>
> Is there some way to get it to remember not to bother mapping certain 
> files as part of the debug server config?
>
> Cheers
> Tom
>
> Dave wrote:
> > Hi Tom, could you generate an xdebug log and attach it here so I can 
> > see what xdebug is doing ? would be good if you could recreate the 
> > problem first, then repeat it with stepping into the file and pressing 
> > continue as described. To generate a log you need to add
> > xdebug.remote_log="c:\xdebug_exe.log"
> > (or select a filename appropriate for your system)
> > to your php.ini file
> >
> > Also what version of php and xdebug are you using ?
> >
> > Regards
> > Dave
> >
> > Tom Walter wrote:
> > > Ever since getting PDT 2, I've had strange issues with breakpoints in 
> > > xdebug.
> > >
> > > Breakpoints set in very high level files are recognised, but those 
> > > that are in files that are a long way down the call hierarchy seem to 
> > > be missed.
> > >
> > > If I 'step into' all the way to a deep file that contains a 
> > > breakpoint, and then click 'continue' the breakpoints seem to be 
> > > recognised there.
> > >
> > > I am using an autoloader, could that effect xdebug's ability to 
> > > correctly locate a file? It seems odd, since if I step into the calls 
> > > I get to the files with the breakpoints fine.