[wdmaudiodev] Re: How to analyze memory dump
- From: fox friend <foxfriend@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Tue, 31 Aug 2004 17:47:45 -0700 (PDT)
Hi Nitin,
I think it is still a problem about your pdb file
path. there is an alternative way to tell what
function it is. You can open your map file, which is
also generated during your sys compilation. Use 0x1b35
minus your map file's offset, which can be found at
the beginning of your map file (eg, 0x1000). Then
result value, say 0x0b35, will be the address that you
search in your map file. Every function contains an
address in the map file, which is its starting point.
And its interval is from this starting point to the
beginning of next function. Find that function whose
interval contains this result value. that's it.
"Nitin Porwal (HCL Technologies Ltd)"
<v-nitinp@xxxxxxxxxxxxx>
Sent by: wdmaudiodev-bounce@xxxxxxxxxxxxx
09/01/2004 08:25 AM
Please respond to wdmaudiodev
To: <wdmaudiodev@xxxxxxxxxxxxx>
cc:
Subject: [wdmaudiodev] Re: How to analyze memory
dump
Does anybody have any idea...??
Please see the mails below...
-----Original Message-----
From: Nitin Porwal (HCL Technologies Ltd)
Sent: Monday, August 30, 2004 1:05 PM
To: 'wdmaudiodev@xxxxxxxxxxxxx'
Subject: RE: [wdmaudiodev] Re: How to analyze memory
dump
Hi Mat,
Thanks for the reply. I did as suggested by you but I
am still not
getting the function name in the stack trace.
Following is the stack
trace given by the debugger. I used "kd -y SymbolPath
-i ImagePath -z
DumpFileName" command for this.
STACK_TEXT:
WARNING: Stack unwind information not available.
Following frames may be
wrong.
f5122c34 804ea221 82252288 ff55e008 806ad190
MyDriver+0x1b35
**************
f5122c58 8055de46 82252288 ff55e008 ff59e028
nt!IoBuildPartialMdl+0xe3
f5122d00 80556cea 0000005c 00000000 00000000
nt!NtWriteFile+0x358a
f5122d34 8052d571 0000005c 00000000 00000000
nt!NtDeviceIoControlFile+0x28
f5122d64 ffffffff f419ad8c 805aca20 00000000
nt!KeReleaseInStackQueuedSpinLockFr
omDpcLevel+0x9fd
804d6da8 805ac673 805ac677 00000000 ffffffff
0xffffffff
ffffffff 00000000 00000000 00000000 00000000
nt!PsGetProcessExitTime+0x685
Am I missing something?
Thanks,
-Nitin
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of
Mathieu Routhier
Sent: Monday, August 30, 2004 12:43 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: How to analyze memory dump
Nitin,
You need to have compiled your driver with "debug
information" and you
also
need the symbols file (.pdb) for that binary, which is
generated by the
compiler. Place your symbols file in the symbols path
of WinDbg and
then
open the crash dump. You should then see the name of
your functions and
variables.
Mat
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of
Nitin Porwal (HCL
Technologies Ltd)
Sent: Monday, August 30, 2004 3:11 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] How to analyze memory dump
Hi,
I have written a driver for a PCI device. Sometimes it
crashes and I
want to debug it. I want to analyze the memory dump
file that is created
at the time of crash on some other machine. I could
only see the bug
check code and stack traces (only function addresses).
How can I see the
function name and source file name which caused the
crash as we see when
we have the debugger hooked up.
For some reasons I can not hook up the debugger with
the machine on
which the driver is installed. So I have the memory
dump file and I want
to know the cause of crash.
Can anybody help me?
Thanks,
Nitin
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator:
mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator:
mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator:
mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
Other related posts:
