This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 163958 - XDebug stops on breakpoint but NetBeans doesn't focus line (file)
Summary: XDebug stops on breakpoint but NetBeans doesn't focus line (file)
Status: RESOLVED DUPLICATE of bug 188844
Alias: None
Product: php
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker with 1 vote (vote)
Assignee: rmatous
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-28 17:31 UTC by gikajavi
Modified: 2013-10-20 10:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gikajavi 2009-04-28 17:31:17 UTC
Product Version: NetBeans IDE 6.5 (Build 200811100001)
Java: 1.6.0_13; Java HotSpot(TM) Client VM 11.3-b02
System: Windows XP version 5.1 running on x86; Cp1252; es_ES (nb)

Servers:
OS: Linux (Fedora 7 2.6.23.17-88 and Ubuntu 9.04 2.6.28-11-generic)
Apache 2 with PHP Version 5.2.4 (Fedora 7). Apache 2 with PHP Version 5.2.6-3ubuntu4 (Ubuntu 9)
XDebug 2.02 (Fedora 7). XDebug 2.04 (Ubuntu 9)


This issue occurs when I trying a remote debug session. Debugging on localhost works fine.
When I init a Xdebug session, if I put a breakpoint in the file index of the project (index.php), Xdebug stops execution
and Netbeans focus the line properly (the line switches to green color) and I can executing step by step. However, if
the breakpoint is in another file, XDebug stops execution but NetBenas doesn't focus the line (if the file related is
not open, NetBean neither opens the file required). NetBeans shows the breakpoint overlayed with the green arrow. The
call stack shows the file and line for my breakpoint. The Local Variables are correctly initialized... All seems ok, but
NetBeans doesn't focus cursor on the breakpointed line. In the same way, if I put a breakpoint on the index file and
then I try to do a step into on a function that is in another file, the same problem occurs.

I always get this issue with a remote web site (FTP) cofiguration. Then I configured samba on my servers (2 with Ubuntu
9.0.4 and a Fedora 7 server) 2 days ago. Surprisingly, in the beginning all works fine with samba config (local web site
on NetBeans project) for all servers, but after the issue come back.

thanks in advance
Comment 1 rmatous 2009-05-05 17:18:55 UTC
There were a couple of fixes that was related to the problem that you describe. Please try the latest development build
and verify that it was fixed or reopen if still doesn't work for you, thanks

development builds download: http://bertram.netbeans.org/hudson/job/PHP-build/
Comment 2 racoon 2010-07-09 11:07:38 UTC
I have the same problem.

Using the latest download available (NetBeans Version 6.9 incl. PHP 1.13.1), the breakpoints works, but I can't see the green line/arrow. The call stack shows the file and line of the breakpoint correctly. When I use the step forward button, it works too and the call stack shows me also the current line. All variable outputs works fine.

My configuration:
- Linux Server with Apache2 and PHP (Debian Lenny)
- Netbeans runs on Windows XP
- accessing to a Samba share: /var/www => //samba/www
- using path mapping: /var/www => //samba/www
- trying to debug a file at //samba/www/test.local/wb/index.php

Do you need more information?


Thank you.
Comment 3 schlaefer 2010-08-08 10:02:38 UTC
I see the same behavior as racoon. Everything seems to work except for the green arrow indicating the breakpoint line.

- Mac OS 10.6.4
- MAMP stack
- Netbeans 6.9.1
Comment 4 Filip Zamboj 2010-08-11 11:52:41 UTC

*** This bug has been marked as a duplicate of bug 188844 ***
Comment 5 francis_55 2013-10-20 10:07:50 UTC
I had the problem described here. I had tried checking the option "Watches and Baloon evaluation" in Netbeans > Tools > Options > Debugging, despite the warning message that this had been known to trigger unstable behavior. The cursor re-appeared when I cancelled the option.