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 228638 - gdb breakpoints not working
Summary: gdb breakpoints not working
Status: RESOLVED WORKSFORME
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: henk89
URL:
Keywords: API
Depends on:
Blocks:
 
Reported: 2013-04-16 23:17 UTC by aschwarz1309
Modified: 2013-04-19 16:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 aschwarz1309 2013-04-16 23:17:47 UTC 
Product Version = NetBeans IDE 7.3 (Build 201302132200)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.6.0_25
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.0-b11

Windows 7 Version 6.1.7601 Service Pack 1 Build 7601

GNU gdb (GDB) 7.6.50.20130408-cvs (cygwin-special)
This GDB was configured as "i686-cygwin".

I just downloaded a new gdb and noticed that breakpoints are not working. I check that the breakpoints were set (Window > Debugging > Breakpoints) and they are their. To ensure that the issue is not path related, I set breakpoints at the first statement in the program after variable setup.

This is a show stopper for me. Any chance someone can look at it soon?
Comment 1 aschwarz1309 2013-04-16 23:32:09 UTC 
Please ignore error posting. I did a cleanup and recompile (and link) and now breakpoints appear to be operating normally. If this is an issue then (for me) it is P4 since I have a solution.
Comment 2 aschwarz1309 2013-04-16 23:46:59 UTC 
I'm sorry to be a pest. I just ran my test again and again no breakpoints. I did a clean compile, no breakpoints. I closed and then reopened Netbeans, no breakpoints. I did a close Netbeans, open Netbeans and a clean compile. No breakpoints. At this point I think the run where breakpoints actually broke was a fluke.

art
Comment 3 aschwarz1309 2013-04-18 19:31:41 UTC 
Please disregard. The problem does not persist. It has occasionally occurred on my laptop but not on my desktop. I can live with it and may well have been operator error.

I am terribly sorry that I caused you additional work.

art