I have a vim71_1 project in ~/NetBeansProjects. The source files are in /usr/local/src/vim71. If I set
Build Result to a non-absolute path then I cannot attach to a running process.
This is because the current implementation prepends the runDirectory if the Build Result is relative.
It then checks if the resulting path is an executable or shared library. If not, the attach fails. It
also doesn't check if Build Result is set (I think it does on Run or Debug).
The fix should do several things: First off, if Build Result (BR) is empty then we should get similar
behavior during attach as we get during Run or Debug. Next, we should look for the exe/so of a relative
BR from the source root or possibly look repeatedly with source root just being one place.
Fixed in http://hg.netbeans.org/main?cmd=changeset;node=e91345591cb6
- create arguments project
- Set project Properties/Build/Linker/Output to "../arguments_1"
- Run project
- Debug project
Error message appears: C:\...\Arguments_1 does not exists or is not an executable
Product Version: NetBeans IDE Dev (Build 200812181401)
Java: 1.6.0_07; Java HotSpot(TM) Client VM 10.0-b23
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)
I tested on Solaris with both an existing and fresh Arguments project and had
no such problem. Next, I tested both existing and fresh Arguments projects on
Vista and had Run fail with the following message in the output window:
/cygdrive/c/nbdev/nbbuild/netbeans/cnd2/bin/dorun.sh: line 103: \
./..\arguments_1: is a directory.
I had a similar failure with Debug, although in that case I got a popup saying
"C:\Users\gordonp\Documents\NetBeansProjects\Arguments_1 does not exist or is
not an executable." I retried with MinGW and got identical behavior.
I'm closing this issue as INVALID. If you can still duplicate the problem then
please open a new issue. This one is about attach failing and reopening it about
Debug failing is a different issue (it makes it harder for me to keep track of
fixes when an issue significantly differs from what it was originally opened as).
The issue is fixed from debugger point of view but described issue exists and should be fixed in 'projects' subcomponent
so I will open a new issue against 'projects' on Windows platform.
fixed in gdb subcomponent
verified in build 20090113092345
Cumulative backport of fixes of IZ 151481(rebackport), 151577, 151610, 153473, 151640, 151761, 155487, 151631, 133134
provided by developer.
Backported into release65_fixes branch
Additional changeset (made on base of http://hg.netbeans.org/main?cmd=changeset;node=e91345591cb6): need to be
backported into release65_fixes:
verified in patch2
With a fully updated Netbeans 6.5 (via "Reload Catalog" in Plugin-Manager) I'm now getting
"The project's Build Result property is not an absolute path."
as an error.
The code for this error message was added in the latest fix for this bug.
Do I understand it right when this should be fixed also in updated versions of Netbeans 6.5? When I try to convert the
project to "Application" type I get the problem described in #159063
How often are the bugfixes released (I have a project where I need "attach to process" quite frequently, and we have a
hard deadline at 2009-04-20 ;-) )?