Re: Corruption of Static data in shared libraries
Re: Corruption of Static data in shared libraries
- Subject: Re: Corruption of Static data in shared libraries
- From: Cameron Hayne <email@hidden>
- Date: Thu, 3 Nov 2005 00:15:42 -0500
On 2-Nov-05, at 9:45 PM, Andrew Kimpton wrote:
I have two shared libraries (CFBundle plugins) which in turn each
load one additional shared library (different for each). I'm
running into a problem where static class variables seem to be
corrupted (often being 'reset' to zero)
This sort of thing might happen if the stack gets too big - e.g. if
you have large arrays on the stack. But I thought that current
versions of gcc had stack-overrun warnings at runtime.
Otherwise look for wild pointers that might be doing the overwriting.
I think you can get gdb to break when a particular location is
written to. Otherwise just narrow in on the problem by printing out
the value of the variable (the one that seems to get corrupted) as
you step through the code.
--
Cameron Hayne
email@hidden
_______________________________________________
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