Stopping an in-progress build can be hazardous to your debugging
Stopping an in-progress build can be hazardous to your debugging
- Subject: Stopping an in-progress build can be hazardous to your debugging
- From: "Mike Pinkerton" <email@hidden>
- Date: Wed, 15 Sep 2004 09:26:24 -0400 (EDT)
- Organization: AOL
I don't want to file a bug because it's not really a reproducible
problem, but I've noticed that it's entirely possible to get the project
into a state where breakpoints no longer stop responding in some, but
not all, files. The debugger simply will not stop, but a printf on that
line verifies that the line is executed.
I'm almost positive that the culprit is stopping a build in the middle
of compiling a file then starting it up again (with or without making
changes to it). I did this several times while iterating on some code in
a debug session and then noticed that all of a sudden gdb would no
longer stop at my breakpoints for that file.
Nothing I did could repair my ability to stop at breakpoints in this
file short of a full clean of the project. Has anyone else noticed this?
I'm not sure how to file a bug since I can't repro most of the time. I'm
sure it'll just get closed outright.
Thoughts?
--
Mike Pinkerton
Mac Weenie
email@hidden http://people.netscape.com/pinkerton/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden