Thanks. This will be my next step. I have already sent several variants of
the program to be tested by my colleague, each with different portions of
the code surrounding this bug removed. I cut out all of the CoreMIDI code
in one variant and just left the first call to CFSTR() and it still crashed.
His results further confirm that CFSTR() seems to be the source of the
problem.
I am curious about the fact that CFSTR() will not create a second copy of an
existing constant string though. As I said before, the crashing code is
only called once, and this is in fact the ONLY code in the entire
application that currently uses CFStrings at all (at least explicitly). I
searched for the string "Bol Processor" in the entire code base and that
exact string is not used anywhere else in the code either.
However, "Bol Processor" is the name of the application. And I DO use that
exact string in the Info.plist file for several properties. Could the
string "Bol Processor" already be instantiated at runtime due to that??
I will try the minimal test app next. I will also try changing the string
"Bol Processor" to something else.
Thanks again for the help!!
Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://anthonykozar.net/
Mike Kluev wrote on 3/10/07 6:20 AM:
> To the original poster. It might be a problem of your setup. Try
> a minimal int main() { CFSTR(""); } app. If that works, start
> with your original app and keep reducing it in binary cut matter -
> that way you'll find a minimal app that still causes a crash.
> At which point you'll probably have better idea what's going on.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
