Crashs while running Device Driver ?

This is a discussion on Crashs while running Device Driver ? within the Symbian forums in Other Technologies category; Hi, I have loaded a device driver and im running the driver. while running the driver my code crash's.. how to handle Memory constraints at ds time..? ( ex.. unloading the driver = or cleanup) Thanks in advance Edited by: Symbian-Developer on 03-Mar-2008 08:24...

Go Back   Application Development Forum > Other Technologies > Symbian

Object Mix

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 03-03-2008, 03:24 AM
symbian-developer
Guest
 
Default Crashs while running Device Driver ?

Hi,


I have loaded a device driver and im running the driver.

while running the driver my code crash's..

how to handle Memory constraints at ds time..? ( ex.. unloading the driver =
or cleanup)



Thanks in advance

Edited by: Symbian-Developer on 03-Mar-2008 08:24
Reply With Quote
  #2  
Old 03-03-2008, 04:06 AM
symbian-developer
Guest
 
Default Re: Crashs while running Device Driver ?

Hi,

I came to know that unloading the device and cleanup is not possible. what'=
s the solution for the cleanup?


thanks

SD/-
Reply With Quote
  #3  
Old 03-03-2008, 04:24 AM
symbian-developer
Guest
 
Default Re: Crashs while running Device Driver ?

Is the crash is in kernel side or User side ?
Reply With Quote
  #4  
Old 03-03-2008, 10:10 AM
markd
Guest
 
Default Re: Crashs while running Device Driver ?

Hi,

Any crashes in a Device Driver will result in a Kernel Panic, as the DD run=
s kernel side, and will display the crash debugger screen asking for a pass=
word.

For this screen you can dump the system value, registers etc.

Also you can install the d_exc application on your target and start it befo=
re running your test.
d_exc will create 2 files for each panic:

d_exc_nnn.txt
d_exc_nnn.stk


Copy both these files to the PC then open the crash log (d_exc_nnn.txt) in =
code explorer.

Provide the symbol files to run the included rofssym tool to decode the cra=
sh log (the decoded log is then opened automatically)

If you scanned the source code (menu item: code explorer - scan source) the=
n you will be able to jump directly from a line of the call stack to the so=
urce code of the corresponding function.



Note that for a KERN-EXEC 3 panic, the most interesting information is in t=
he registers rather than the stack

Mark
Symbian


Reply With Quote
Reply


Thread Tools
Display Modes


All times are GMT -5. The time now is 07:22 AM.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
vB Ad Management by =RedTyger=

In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.