• 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: mach in signal handler
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mach in signal handler


  • Subject: Re: mach in signal handler
  • From: Michael Smith <email@hidden>
  • Date: Sun, 4 Feb 2007 12:29:48 -0800


On Feb 2, 2007, at 11:28 PM, Cyrus Harmon wrote:


On Feb 1, 2007, at 10:04 PM, Terry Lambert wrote:
A good example would be "malloc": it's always wrong to allocate or free memory in a signal handler.

Hmm... I suppose if malloc is off limits, you're probably going to tell me I can't call vm_allocate either. damn.

Actually, you can probably get away with that. There are possibilities for deadlock in low memory situations, but they are systemic and nothing works well when you can't provide physical pages in a timely fashion, so you would have good company.


 = Mike

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


References: 
 >mach in signal handler (From: Steve Checkoway <email@hidden>)
 >Re: mach in signal handler (From: Terry Lambert <email@hidden>)
 >Re: mach in signal handler (From: Cyrus Harmon <email@hidden>)

  • Prev by Date: Re: Walking the task list from a kext
  • Next by Date: Re: Debugging Proprietary KEXTs
  • Previous by thread: Re: mach in signal handler
  • Next by thread: Re: mach in signal handler
  • Index(es):
    • Date
    • Thread