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 118570 - Non existing files in breakpoint
Summary: Non existing files in breakpoint
Status: CLOSED WORKSFORME
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ gordonp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-11 16:20 UTC by avp
Modified: 2009-06-25 10:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
New project with all files (130.43 KB, application/octet-stream)
2007-10-12 13:35 UTC, avp 		Details
New project with all files (130.43 KB, application/x-gzip)
2007-10-12 13:35 UTC, avp 		Details
Project with deleted files (104.44 KB, application/octet-stream)
2007-10-12 13:37 UTC, avp 		Details
Log (39.62 KB, text/plain)
2007-10-12 15:31 UTC, avp 		Details
Screen (376.59 KB, image/png)
2007-10-12 15:33 UTC, avp 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description avp 2007-10-11 16:21:01 UTC 
Steps to reproduce:
1. Create new file;
2. Write code and step breakpoint
3. Run debugger, all works
4. Delete file created in 1.
5. Run debugger - debugger session started and :(( hang

Netbeans 6.0 (1010) SUSE 10.2
Comment 1 avp 2007-10-11 16:22:32 UTC 
Sorry, forgot.
When I delete breakpoint in breakpoint window all works.
Comment 2 Alexander Pepin 2007-10-11 16:52:58 UTC 
If you delete a file then try to debug the project an error windows appears and says:
"The project is empty. You will need to add a file to the project before you can build it."
Comment 3 avp 2007-10-12 07:33:28 UTC 
In projects I have more then one file. And when I delete one file in which was breakpoint I can't run debugger.
Comment 4 avp 2007-10-12 07:33:39 UTC 
In projects I have more then one file. And when I delete one file in which was breakpoint I can't run debugger.
Comment 5 Alexander Pepin 2007-10-12 12:33:23 UTC 
can not reproduce the bug using the following scenario:
- create a new project
- add a main C++ file (newmain.cc)
- add an empty C++ file (newfile.cc)
- put some code into the empty file (newfile.cc)
- set a breakpoint in the newfile.cc
- do step into, everything is OK
- stop debugger
- delete newfile.cc, the breakpoint is still visible in Breakpoints window
- do step into, everything is OK

please provide an exact scenario to reproduce the bug
Comment 6 avp 2007-10-12 13:35:14 UTC 
Created attachment 50811 [details]
New project with all files
Comment 7 avp 2007-10-12 13:35:38 UTC 
Created attachment 50812 [details]
New project with all files
Comment 8 avp 2007-10-12 13:37:01 UTC 
Created attachment 50813 [details]
Project with deleted files
Comment 9 avp 2007-10-12 13:39:31 UTC 
Sorry for duplicated attachments :(.
In first project exists newfile.h and newfile.cc in .cc file I has set breakpoint.
In second project I delete newfile.h and newfile.cc and run debugger.
Comment 10 Alexander Pepin 2007-10-12 14:40:36 UTC 
Anyway I can not reproduce the bug neither on Linux nor on Windows. Please try the latest build 20071012.
Comment 11 avp 2007-10-12 15:30:07 UTC 
I add to attachments:
1. Screen with running debugger - his is hang
2. Log with backtrace
Comment 12 avp 2007-10-12 15:31:03 UTC 
Created attachment 50830 [details]
Log
Comment 13 avp 2007-10-12 15:33:00 UTC 
Created attachment 50831 [details]
Screen
Comment 14 _ gordonp 2007-10-18 17:52:01 UTC 
Can you run netbeans with "-J-Dgdb.console.savelog=true" and attach the log file? It should be
named something like /tmp/gdb-cmds*.log (you'll get a different number for '*' each time you run,
if there are more than 1, take the most recent where you had this hang).
Comment 15 Alexander Pepin 2007-11-26 14:17:23 UTC 
I tried to reproduce the issue in the latest build and couldn't.
Please update the issue if you still can reproduce it.
Comment 16 avp 2007-11-26 15:54:18 UTC 
No, I run my earlier test-project (where this error was raised ) - nothing. All work. :).