help trying to locate sigsegv error please
help trying to locate sigsegv error please
- Subject: help trying to locate sigsegv error please
- From: Ben Dougall <email@hidden>
- Date: Thu, 14 Aug 2003 20:23:30 +0100
does the fact that my app exits, always with the same input with signal
11 (SIGSEGV) sporadically, strongly point towards a memory management
problem? the reason i mention 'same input' and 'sporadically' is
because i'm doing a lot of stepping along and reading data from an
NSData object using a pointer gained by -bytes and adding adding
another variable to that pointer, so over run is a possibility there
and that error could be caused by over run like that? but the same
input sometimes crashes, sometimes doesn't, so for that reason i don't
think it is over stepping - it would over run every time and exit with
signal 11 sigsegv every time right?
signal 11 (SIGSEGV) is cuased by attempting to access something that i
shouldn't be - is that correct? so releasing / deallocating an object,
then trying to access it in some way would give that error for sure?
i haven't got a clue what's causing it. there's quite a lot of code
but all the alloc and init situations, which there aren't many of, are
tallied to releases and there are no extra releases.
can it be cause by not releasing something?
why sporadic? << that seems odd to me.
i don't know which part is causing the problem, and the whole thing is
too much code to post. suggestions? please :)
thanks, ben.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.