• 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
[Solved] Re: Kernel Panic Cluedo
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Solved] Re: Kernel Panic Cluedo


  • Subject: [Solved] Re: Kernel Panic Cluedo
  • From: Stephane <email@hidden>
  • Date: Thu, 23 Nov 2006 20:10:30 +0100


On Nov 22, 2006, at 6:04 PM, Michael Smith wrote:

Stephane wrote:
When you do some bad things in your Kernel Extension (such as writing where you should not, reading a bit too far in buffers, etc...), should a Kernel Panic occur in your Kernel Extension or can it occur later?

It depends on what you damage. If you read/write completely out of bounds, your code will fail. But if you destroy a pointer belonging to someone else, there is no way for the hardware/kernel to know a) that that's what you're doing, or b) to blame you when some other code attempts to use it.

It turned out to be a copyin of a bigger size than required.

It could be cool if there was a Kernel simulator with memory protection...


_______________________________________________ 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
  • Follow-Ups:
    • Re: [Solved] Re: Kernel Panic Cluedo
      • From: Michael Smith <email@hidden>
References: 
 >Kernel Panic Cluedo (From: Stephane <email@hidden>)
 >Re: Kernel Panic Cluedo (From: Michael Smith <email@hidden>)

  • Prev by Date: Re: Kernel Panic Cluedo
  • Next by Date: Re: [Solved] Re: Kernel Panic Cluedo
  • Previous by thread: Re: Kernel Panic Cluedo
  • Next by thread: Re: [Solved] Re: Kernel Panic Cluedo
  • Index(es):
    • Date
    • Thread