Re: Distributed Objects - setting protocol crashing GCC 4.0 - CAUSE DISCOVERED
Re: Distributed Objects - setting protocol crashing GCC 4.0 - CAUSE DISCOVERED
- Subject: Re: Distributed Objects - setting protocol crashing GCC 4.0 - CAUSE DISCOVERED
- From: Jeremy Dronfield <email@hidden>
- Date: Tue, 11 Apr 2006 14:59:40 +0100
On 11 Apr 2006, at 10:20 am, Jeremy Dronfield wrote:
On 11 Apr 2006, at 4:51 am, email@hidden wrote:
I'm only replying to Cocoa Dev, since this seems off-topic for
XCode Users.
Almost 3 years ago, Wade Tregaskis posted Cocoa-Dev that -
setProtocolForProxy: caused GCC 3.0 to crash with an internal bus
error. John C Randolph asked him to submit a bug report, and it
sounded as if the issue had been recognised within Apple.
Does anyone know what happened with this, because I'm seeing it
now, nearly 3 years later - the same "internal bus error" crash,
with Xcode 2.2.1 and GCC 4.0, when calling -setProtocolForProxy:.
Apparently I never filed a bug report for this... at least, I
can't find it, if I did. I can't remember the details now, so
you'd best file one yourself. Send me the radar # when you do.
What's curious is that while I vaguely remember this problem, it
apparently didn't become a showstopper for what I was working on
at the time. So there may be some satisfactory workaround. If
that's not covered in the archives, remind me now what the details
of the problem are and it might jog my memory.
Before filing a bug, I'll try using a test project, in case there's
some issue in my application project which is causing -
setProtocolForProxy: to choke the compiler.
I've pinpointed the cause, though I still don't understand it:
1. Created a test project, using the same source files as my real
project. Compiled with no problems. So it's not a Cocoa issue. Maybe.
2. Painstakingly duplicated all the build settings from my real
project into my test project. Build... CRASH!!
So it's presumably an Xcode issue. Or maybe not. Compared build
settings. Only suspicious difference is prefix headers. Tried
switching off prefix header precompilation - problem gone... Went
back to my real project and switched off precompilation. Same result:
no build problems.
But then, creating a new test project, with a precompiled prefix
header and calling -setProtocolForProxy:. Again, no problem. Huh?
Looks like I'm going to have to comb through every line of my project
to try and find the cause.
Regards,
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden