What to do about "clobbered by `longjmp' or `vfork'" warnings?
What to do about "clobbered by `longjmp' or `vfork'" warnings?
- Subject: What to do about "clobbered by `longjmp' or `vfork'" warnings?
- From: j o a r <email@hidden>
- Date: Wed, 3 Dec 2003 10:56:08 +0100
In our deployment builds we get a lot of warnings like this when we use
NS_DURING exception handlers:
"variable `xxx' might be clobbered by `longjmp' or `vfork'"
I don't know if the code is really broken, or if GCC is just not able
to interpret it correctly - but I think that the blame lies with GCC. I
also don't know of any way we can reliably warp our code so that it no
longer generate warnings. Using the "volatile" qualifier has been
mentioned, but is probably not the right way to solve the problem (?).
We are also not able to move to the new style of exception handling
introduced with Panther, as we need to build for older versions of Mac
OS X. As I see it, we probably need to disable these warnings.
This is our current "Other Warning Flags" string:
"-Wall -W -Wno-unused-parameter -Wfloat-equal -Wwrite-strings
-Wno-sign-compare"
"man GCC" seems to think that the warning in question is caused by
"-Wuninitialized", that is a part of "-Wall". I tried to silence the
warning by adding this to our string of compiler warning flags:
"-Wno-uninitialized"
..but still got the clobbered-warnings. I'm also not happy about
having to turn off warnings for non-initalized automatic variables. Why
are these two things covered by the same warning flag?
Ideas?
j o a r
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.