problems/bugs in xCode
problems/bugs in xCode
- Subject: problems/bugs in xCode
- From: Jonny Taylor <email@hidden>
- Date: Fri, 24 Jun 2005 16:17:29 +0100
Hi,
I'm another refugee from CodeWarrior, and I've been working on a small
project to grips with xCode before attempting to migrate my existing large
projects. In many ways I prefer xCode, but I've come across a few apparent
bugs along the way. I was wondering if they are well-known and if there are
known workarounds for them. I'm on a dial-up connection at the moment, but I
will of course file bugs where appropriate once I'm back on broadband...
I'm running Tiger, xCode 2.1.
The most serious is that when debugging, the debugger has a habit of
aborting when I click around in the call stack. This seems to be connected
with a 200MB array I have defined as a global; if I halve its size I don't
see any problems. The message I get is:
==========
gdb-powerpc-apple-darwin(6833,0xa000ef98) malloc: ***
vm_allocate(size=536875008) failed (error code=3)
gdb-powerpc-apple-darwin(6833,0xa000ef98) malloc: *** error: can't allocate
region
gdb-powerpc-apple-darwin(6833,0xa000ef98) malloc: *** set a breakpoint in
szone_error to debug
out of memory allocating 536871000 bytes
The Debugger has exited with status 1.The Debugger has exited with status 1.
==========
Some other gripes:
When debugging, if you step over a fprintf(stderr, ...), xCode behaves as
if you pressed "Continue" instead of "Step Over".
Build often doesn't recompile dirty source files - I almost always need to
alter, not save, explicitly compile and then build before my changes are
picked up.
When I choose "Show Assembly Code" for my 1-file project several times over
the course of a session, it compiles 1 more source file every time (i.e. the
third time I do it it claims to be "compiling 3 source files", and does
indeed take 3 times as long to do its stuff). Quitting xCode (and I think
closing the project) resets this.
Use arrow keys to navigate debugger call stack and the code displayed below
doesn't update like it does if you click somewhere else in the call stack.
Is there a way of getting source code to show up in Shark when looking at a
disassembly? I know that on a release build there's likely to be a lot of
reshuffling of code, but having anything there at all would be better than
just reading a long function in pure assembly and trying to work out what
assembly corresponds to what source from where it calls other functions,
etc...
In particular, workarounds for the first 3 problems would be highly
appreciated if anybody can give me any suggestions, because they're slowing
me down a lot!
Cheers
Jonny
_______________________________________________
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