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 178200

Summary:	Rails debugger won't catch breakpoints when project's path includes a symbolic link
Product:	ruby	Reporter:	jackoshanter
Component:	Debugger	Assignee:	issues@ruby <issues>
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	6.x
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:

Description jackoshanter 2009-12-06 06:39:27 UTC

Creating a Rails project from an existing source who's path includes at least one symlink will cause the debugger to miss breakpoints.


Steps to reproduce:

$ cd ~
$ rails testapp-v0.1
$ ln -s testapp-v0.1 testapp

Now create a project from /home/user/testapp

Ruby Platform: Ruby 1.8.7
Server: WEBrick

Comment 1 Erno Mononen 2009-12-08 04:22:26 UTC

Thanks for the report. This is likely a problem in the ruby-debug-ide gem; need to be fixed there.

Comment 2 rockorequin 2011-01-19 08:44:14 UTC

This is still present in 7.0beta.

Note the following observation:

a) If I double click on the file name in the Projects navigator, eg items_controller.rb, netbeans will open this file (as expected) in the editor, but any breakpoints that I set in this edit window are never hit.

b) If then I double click on the same file name in the "Output - Webrick" window, ie when it appears as part of a stack trace after an error, a second window will be opened also called items_controller.rb in the editor. Importantly, breakpoints then work fine in this second window.

So an easy(?) fix for this might be to make the Project navigator resolve file paths in the same way as the Output window does.