Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » PHP Development Tools (PDT) » problems with breakpoints in xdebug in PDT2
problems with breakpoints in xdebug in PDT2 [message #93484] Thu, 12 February 2009 01:46 Go to next message
Eclipse UserFriend
Originally posted by: eclipsenews.20.epm.spamgourmet.com

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.
Re: problems with breakpoints in xdebug in PDT2 [message #93508 is a reply to message #93484] Thu, 12 February 2009 07:36 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dkel50.hotnospmail.com

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.
Re: problems with breakpoints in xdebug in PDT2 [message #93605 is a reply to message #93508] Fri, 13 February 2009 03:12 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: eclipsenews.20.epm.spamgourmet.com

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.
Re: problems with breakpoints in xdebug in PDT2 [message #93619 is a reply to message #93605] Fri, 13 February 2009 10:09 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dkel50.hotnospmail.com

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.
Re: problems with breakpoints in xdebug in PDT2 [message #93808 is a reply to message #93619] Mon, 16 February 2009 03:35 Go to previous message
Eclipse UserFriend
Originally posted by: eclipsenews.20.epm.spamgourmet.com

Hi again,

Actually I found a workaround. For anyone else that needs it: if you
manually setup the mapping in the debug server config dialog, then you
can map a specific file directly, rather than a whole path. You can even
choose a location outside your project root. So in my case I copied the
bootstrap to my local HD, but outside my project, and setup a mapping of
just that one specific file.

It would be good if the dialog that pops up to ask you how to map a file
had a checkbox that specified whether you want to map just the one file,
or everything with the same path as that file. I can see how mapping the
whole path is convenient if it turns out that there are a lot of files
in the same location. But given that the dialog asks how to map a
specific file, it was not obvious that this is what would happen.

Anyway thanks for all your help, and I appreciate the effort you've put
into the debugger, now I've figured it out it's fantastic!

Tom

Dave wrote:
> 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.
Previous Topic:Publishing in new PDT?
Next Topic:Reading info from plugin.xml
Goto Forum:
  


Current Time: Tue Jan 31 21:23:49 GMT 2023

Powered by FUDForum. Page generated in 0.05946 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top