title: How to implement an abstraction layer over VxWorks to provide handles for exception handling & memory management?
body: <p>I have just started working on VxWorks. I am currently working on the following :-</p>
  
  <p>I need to create a framework which will encompass exception handling &amp; memory management (detecting null pointer usage, for instance). All in all, it will be like an abstraction layer over the operating system. This framework will be in the form of a downloadable kernel module. Unit tests (also DKM's) would draw from this framework. </p>
  
  <p>I want to manipulate the exception handlers &amp; handle them myself, but I don't know how. </p>
  
  <p>The ED&amp;R component needs to be configured with the kernel image in order to work with certain API'S (if i understand correctly), but if its a DKM which is already in kernel space, doesn't it have complete access to the memory (RAM, persistent memory) &amp; hence can directly gain access ?</p>
  
  <p>Can you provide me with some guidelines as to how I should go about achieving my objective ? </p>
  
  <p>Currently, when an exception occurs, after displaying some details, the task stops &amp; I get a prompt to debug the module. Afterwards, to see the core dump, I use the command edrShow.                  </p>
  
  <p>What I want to do is, get rid of the debug prompt &amp; after the task stops, display the core dump to the user without having to explicitly issue the command.                                       </p>
  
  <p>I did look into edrStub.c (edrKernelFatalPolicyHandler method) but I haven't been able to figure out how to manipulate it to get the desired result.</p>