Bugzilla – Full Text Bug Listing
| Summary: | remove breakpoint fails in editor | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | michel kollenhoven <eclipse> | ||||||||||
| Component: | PDT | Assignee: | PHP Debug <php.debug-inbox> | ||||||||||
| Status: | NEW --- | QA Contact: | |||||||||||
| Severity: | minor | ||||||||||||
| Priority: | P3 | CC: | eclipse, stu, zhaozhongwei | ||||||||||
| Version: | unspecified | ||||||||||||
| Target Milestone: | --- | ||||||||||||
| Hardware: | PC | ||||||||||||
| OS: | Windows XP | ||||||||||||
| Whiteboard: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
michel kollenhoven
Could you obtain an xdebug.log of the problem ? It needs to capture the setting of the breakpoints, then the removal. You can get info about how to do that from http://www.eclipse.org/pdt/docs.php Xdebug 2.0 guide. Or go to http://www.xdebug.org for info on configuring xdebug Created attachment 176654 [details]
screen shot for xdebug.log
note info.php is opend twice
as
/aisa/www/inf.php (by project)and as
c:\cvs cs\aisa\www\info.php
Created attachment 176655 [details]
xdebug communication log
the xdebug log file
unfortunately the log doesn't show the problem occurring. In this log each of the breakpoint removes was successful. It does show however that you are generating duplicate breakpoints, which I suspect is because you are putting the breakpoints on 2 different files in the eclipse editor, but they both map to the same file in reality. If you could get an xdebug log when the error occurs that would be great. hmmm the log was not so replicateble as i thought... but still i have breakpoints i cant remove form the editor i get a red text in status bar: breakpoint cannot be set at this point note that this is on remove of the brakpoint if i come to this agen i will send you the log, but still it not the source of the problem(getting a file system file instead of a local file ah, ok I understand now. You are describing an issue with the editor when trying to remove a breakpoint. What I was looking into was why xdebug was responding with "no such breakpoint". If incorrect information is being sent due to the breakpoint manager being confused then that would explain it. I think someone else from the PDT development group may need to look into this. Yes,I think this bug is caused by the path.It seems that pdt consider www/info.php and c:..../www/info.php be different files,but it is the same file actually.Indeed there are two php editors opened for this file for different path. Created attachment 176874 [details]
xdebug transaction log
sorry no steps for this one
good luck
btw remote debugging my debian server displays a dialog(somthing about paths or files remote=>local) the first time and keeps one editor open(the project path not the full path) but my local windows debug fails Created attachment 176979 [details]
xdebug communication log
this one is better
note i had the brakpoints before debugging from brouwser and removed them during debugging
Could the path issue could be related to this bug? https://bugs.eclipse.org/bugs/show_bug.cgi?id=329496 I'm seeing both these bugs happen now. When I'm debugging my web server, sometimes client applications send 1000's of messages at a time. When I set a breakpoint to look at one of them, and then REMOVE the breakpoint, the other 999 messages still come in and also break, even though the BP has been removed! My only option is to restart Apache in order to remove the breakpoint. This is a huge issue for me. Thanks! no there is no nw instance started in this case( at leas not with my code) note i do not devolep on win32 (ubuntu 64 now) but i think i can reproduce in linux |