EXC_BAD_ACCESS when running from different drive
EXC_BAD_ACCESS when running from different drive
- Subject: EXC_BAD_ACCESS when running from different drive
- From: Stefan Werner <email@hidden>
- Date: Tue, 27 Sep 2005 14:31:18 -0700
Hi,
I have a really bizarre problem:
I developed a program on my PowerBook G4, under 10.4.2 with Xcode 2.1/
gcc4, using an external CVS for version control. From time to time
I'd do a clean checkout from CVS to my external FW drive and build/
run it from there.
Now I'm sitting at a 1.6 GHz PowerMac G5, 10.4.2, Xcode 2.1. When I
check out the source code from CVS and build it, it crashes with
EXC_BAD_ACCESS in (Carbon) CopyPascalStringToC(). When I build and
run it from my FireWire drive, it runs fine. When I copy the build
product from the G5's internal drive to the FW drive, it runs. When I
copy the binary built on the FireWire drive to the internal hard
drive and run it from there, it crashes. When I copy the file to the
second partition of the G5's internal boot drive, it crashes.
What on earth could be triggering this? The path name on the internal
G5 drive is shorter than the one on the internal drive, so it's
unlikely to be some hidden buffer overrun. The debugger shows me that
in both cases I'm passing the exact same pointers to
CopyPascalStringToC with the exact same memory content.
Thanks for any help solving this puzzle,
Stefan
_______________________________________________
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