Re: XCode 2.1 breakpoints not working for command line apps?
Re: XCode 2.1 breakpoints not working for command line apps?
- Subject: Re: XCode 2.1 breakpoints not working for command line apps?
- From: Jim Ingham <email@hidden>
- Date: Mon, 11 Jul 2005 10:50:19 -0700
One thing you can do is to keep the gdb/Xcode logging on. That way,
when you encounter a problem, you will have the transcript there, and
at least we can tell what commands caused the hang, whether it was
gdb or Xcode, etc... The way to do this is:
1) Quit Xcode.
2) In Terminal, say:
$ defaults write com.apple.Xcode PBXGDBDebuggerLogToFile YES
Then for every Xcode debugging session, you will get a file in /var/
tmp/folders.<PID>/TemporaryItems with a name like:
XCGDB-<Program Name>-<XCode PID>
This probably slows down Xcode marginally, but I run with it on all
the time, and I don't notice it...
Another thing to do is if Xcode hangs during a debugging session,
sample both Xcode, and the gdb-powerpc-apple-darwin processes. You
can either use the Sample.app in /Developer/Applications/Performance
Tools, or from the command line do something like:
$ sample <PID> 20 10
These will also help us to see whether one or the other process has
gone wrong, or if somebody dropped a message and both are just
waiting for the other to respond, or something like that...
If you can gather this information please file a bug with it. We may
not be able to figure out what's going on without a reproducible
case, but sometimes this is enough information for us to see what's
happening by itself.
Thanks,
Jim
On Jul 9, 2005, at 6:49 AM, João Varela wrote:
On 2005/07/08, at 16:47, email@hidden wrote:
From: Arshad Tayyeb <email@hidden>
Subject: Re: XCode 2.1 breakpoints not working for command line apps?
To: Ladd Van Tol <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Turning off the "Load symbols lazily" option worked for me. It's
not optimal, but at least it's letting me use the debugger now.
Thanks!
-Arshad
On Jul 7, 2005, at 11:17 PM, Ladd Van Tol wrote:
I had a similar problem setting breakpoints in C++ code that I was
only able to resolve by turning off the "Load symbols lazily"
option in the Xcode debugging prefs.
I am uncertain why this worked, and Xcode 2.1 debugging continues
to be slow and flaky in many other regards.
- Ladd
Today I also ran into problems with debugging my C++ tool (which
had never happened before) because GDB would hang after some time
if I tried to step in or step over. The hang would not happen if I
just hit continue and the tool would exit normally. I then tried to
find if there was a reproducible case. I activated two breakpoints
in different source files and it did hang in the same place (3
times after executing a while loop). I went to the target of my C++
tool in XCode and deactivated the zero link option. Then I rebuilt
my tool and the hang did not happen again. I then cleaned up my
target, activated zero link, and rebuilt it and tried to debug it
so that I could reproduce the hang and file a bug. However, this
time the hang did not happen even with zero link activated.
So, I have to agree that debugging with XCode GUI is sometimes
flaky. Sometimes it works, sometimes it doesn't, which is not very
helpful for reporting a reproducible bug. I'll keep a watchful eye
if I can find a reproducible situation and file a bug on this.
- João
_______________________________________________
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
_______________________________________________
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