• 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: Segfault when releasing autorelease pool
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Segfault when releasing autorelease pool


  • Subject: Re: Segfault when releasing autorelease pool
  • From: j o a r <email@hidden>
  • Date: Mon, 31 Oct 2005 07:41:47 +0100


On 31 okt 2005, at 04.28, Sean McGroty wrote:

When I attempt to free the autorelease pool, the program crashes with a segmentation fault.
It has to be related to the initWithSerialDeviceFileName code, as allocating and initializing the base class of GDFreestyleMeter, GDMeter, works properly. Specifically, the problem appears to center on the "meterDevice = [NSFileHandle fileHandleForUpdatingAtPath:deviceFile];" line in initWithSerialDeviceFileName, as commenting that out allows the program to quit successfully, at the cost of not doing anything useful.
What am I doing wrong?

A crash when releasing an autorelease pool is likely due to over- releasing one of the contained objects. Enable the use of NSZombie's (see docs and list archives) in your app to see what type of object that is.


j o a r



Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Segfault when releasing autorelease pool (From: Sean McGroty <email@hidden>)

  • Prev by Date: Re: Uptime to Date/time
  • Next by Date: Enable Accessibility Directly
  • Previous by thread: Re: Segfault when releasing autorelease pool
  • Next by thread: Binding Problem: Displaying a new NIB fails; but a duplicate of an existing/working NIB does display.
  • Index(es):
    • Date
    • Thread