how to track dump file

Ashish

unread,

Nov 3, 2009, 3:38:33 AM11/3/09

to

i have crashed dump file (.mdmp and .hdmp). it contains crash of an
application.
I have windbg and OS symbold installed on my system but could not get the
position where crash occur in application
please suggest how to use windbg properly to know thw crash place.

Jochen Kalmbach [MVP]

unread,

Nov 3, 2009, 3:50:27 AM11/3/09

to

Hi Ashish!

"Open crash dump..."
.symfix+
!analyze -v

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

Ashish

unread,

Nov 3, 2009, 6:12:25 AM11/3/09

to

> "Open crash dump..."
> .symfix+
> !analyze -v

Yes i open crash dump.
What is .symfix and what to analyze.
please explain in detail
"Jochen Kalmbach [MVP]" <nospam-Joch...@holzma.de> wrote in message
news:%23UQjyKG...@TK2MSFTNGP02.phx.gbl...

Jochen Kalmbach [MVP]

unread,

Nov 3, 2009, 6:20:54 AM11/3/09

to

Hi Ashish!

>> "Open crash dump..."
>> .symfix+
>> !analyze -v
>
> Yes i open crash dump.
> What is .symfix and what to analyze.
> please explain in detail

What is your output, after you type "!analyze -v"?

Ashish

unread,

Nov 3, 2009, 7:33:27 AM11/3/09

to

Ok i got the function where problem occur after typing "!analyze -v"
can i debug in it

"Jochen Kalmbach [MVP]" <nospam-Joch...@holzma.de> wrote in message

news:ud8d2eHX...@TK2MSFTNGP02.phx.gbl...

Jochen Kalmbach [MVP]

unread,

Nov 3, 2009, 8:21:26 AM11/3/09

to

Hi Ashish!

> Ok i got the function where problem occur after typing "!analyze -v"
> can i debug in it

Is this a question or a statement?

Ashish

unread,

Nov 4, 2009, 3:01:54 AM11/4/09

to

It's a question.
Windbg shows all functions where crash occur.
Can we debug the code?
When i try VS2005/2008 it's not showing same crash(as shown by windbg) so i
can not debug in vs2005/2008

"Jochen Kalmbach [MVP]" <nospam-Joch...@holzma.de> wrote in message

news:ON4KNiIX...@TK2MSFTNGP02.phx.gbl...

Jochen Kalmbach [MVP]

unread,

Nov 4, 2009, 6:12:41 AM11/4/09

to

Hi Ashish!

> It's a question.
> Windbg shows all functions where crash occur.
> Can we debug the code?

In a crash dump, you can only "examine" the crash. Of course, this is
mostly called "debugging". But you cannot execute or step through the code.

> When i try VS2005/2008 it's not showing same crash(as shown by windbg) so i
> can not debug in vs2005/2008

WinDbg is more powerfull than VS ;)

duttaa...@gmail.com

unread,

Nov 4, 2009, 6:41:42 AM11/4/09

to

Can I get the exact statement where my crash did occur? I can see the
call stack. Can I go to a specific frame and print the source code in
human readable form?

Thank you
Abhijit Dutta

On Nov 4, 4:12 pm, "Jochen Kalmbach [MVP]" <nospam-

Ashish

unread,

Nov 4, 2009, 7:51:07 AM11/4/09

to

Thanks I understood.
Dump file is use in case when any application crash very rarely. SO it's
very difficult to regenerate the crash again. Only dump file show the crash.
If i found some crash dump file and i fix it in my application is there any
way to check modified application with dump file. Means when i run
application with dump file then it should not crash.

"Jochen Kalmbach [MVP]" <nospam-Joch...@holzma.de> wrote in message

news:eaEt7%23TXKH...@TK2MSFTNGP06.phx.gbl...

Jochen Kalmbach [MVP]

unread,

Nov 4, 2009, 8:16:08 AM11/4/09

to

Hi duttaabhijeet!

> Can I get the exact statement where my crash did occur? I can see the
> call stack. Can I go to a specific frame and print the source code in
> human readable form?

If you have debug-symbols, then this is the "default behavior".
You need to have pdb-symbols. This can also be generated in release builds.
If you have the *exact same* source you can generate the pdb-file also
afterwards (if you use the same compiler/linker ettings) and then you
can load the pdb if you tell WinDbg to load "anything":

.symopt +0x40
.sympath+ c:\Path\to\pdb
.reload
!analyze -v

Then if should display a "human readable" callstack.