• 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: Kernel extension debugging tool?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Kernel extension debugging tool?


  • Subject: Re: Kernel extension debugging tool?
  • From: Quinn <email@hidden>
  • Date: Fri, 18 Nov 2005 10:02:06 +0000

At 18:52 -0800 16/11/05, Rob Barris wrote:
And we only really intercept and track mallocs() & frees() that are called directly from our code, if something in Carbon or GL or BSD is doing double frees or write-after-free, we won't know about it.

You can intercept the system mallocs if you want. The only gotcha is that (the only supported way to do this requires that) you must run single namespace. Let me know if you'd like to see the details.


S+E
--
Quinn "The Eskimo!"                    <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Kernel extension debugging tool? (From: Sam Vaughan <email@hidden>)
 >Re: Kernel extension debugging tool? (From: Rob Barris <email@hidden>)

  • Prev by Date: Re: kCFStreamPropertyHTTPAttemptPersistentConnection
  • Next by Date: SystemConfiguration problem with Proxy
  • Previous by thread: Re: Kernel extension debugging tool?
  • Next by thread: Airport Dialog & bundles
  • Index(es):
    • Date
    • Thread