• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: help trying to locate sigsegv error please
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: help trying to locate sigsegv error please


  • Subject: Re: help trying to locate sigsegv error please
  • From: Ben Dougall <email@hidden>
  • Date: Fri, 15 Aug 2003 11:44:45 +0100

On Friday, August 15, 2003, at 12:59 am, publiclook wrote:

run your application in the debugger. When it crashes, the debugger will show you where and why.

i had tried that and nothing happened. no information, no error. i don't think i'd left it long enough to fail though. it must go much slower under gdb.

turned out i was over-running the data.

thanks.



On Thursday, August 14, 2003, at 03:23 PM, Ben Dougall wrote:

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.
_______________________________________________
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.

  • Follow-Ups:
    • RE: help trying to locate sigsegv error please
      • From: "Jonathan E. Jackel" <email@hidden>
    • Re: help trying to locate sigsegv error please
      • From: "Alastair J.Houghton" <email@hidden>
References: 
 >Re: help trying to locate sigsegv error please (From: publiclook <email@hidden>)

  • Prev by Date: Recent Items
  • Next by Date: Re: Recent Items
  • Previous by thread: Re: help trying to locate sigsegv error please
  • Next by thread: Re: help trying to locate sigsegv error please
  • Index(es):
    • Date
    • Thread