WinDBG tool not able to respond to my vc++ application crash

Question

0.00/5 (No votes)

See more:

Hi,

I have installed WinDBG tool (dbg_x86_6.9.3.113)in my windows XP .
Then I register WinDBG by using command "Windbg -I"

For generating a crash-dump ,I hv created a simple dialog based application which
creating a crash(application-crash).

I put the Symbol file(.PDB) of this application in side a new folder under C-drive .Under C-Drive WinDBG is also installed .

In 'Symbol file path...' i gave this new folder's path.

But while my application getting crashed the tool not able to generate log.

I hve searched in google, but i'm not getting any new thing(step) which i have not followed.

Can any one please guide, whether i'm skipping any step to use WinDBG to generate log for analysis.

Or else please send me the proper steps(n detail) to generate dump. So that i'll check once whether i skipped any steps.

PLease help soon. Thanks

Posted 22-Aug-12 10:58am

litu kumar

Updated 22-Aug-12 20:44pm

v5

Add a Solution

Comments

Shaunak De 7-Sep-12 4:45am

You can use VS itself to debug. It may be easier than WinDbg. Does your app crash at startup or a after some operation is done. If it can be made to start up, you can attach the VS debugger to it.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Blake Miller · Answer 1 · 2012-12-20T07:36:00

Solution 1

And if you REALLY want to debug your application, insert a DebugBreak() function call into it somewhere convenient - based on a button, or user action, or even close to its startup.

Posted 20-Dec-12 7:36am

Blake Miller

Mattias Högström · Answer 2 · 2012-12-29T07:32:00

I dont use automatic saving of memory dumps myself.
I always either store the memory dump manually or attach windbg while it is running.

The TaskManager can store memory dumps.
Right click on a process and select "Create Dump File".

If you run under x64, you will need to use the 32 bit version of TaskManager to create a 32 bit dump. Otherwise it will be saved in Wow64 mode, which only gives problems.
C:\Windows\SysWOW64\TaskMgr.exe 32 bit version

An alternative is to use ProcDump from sys internals for storing dumps. It automatically chooses the correct format.
http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx[^]

Apart from adding your own pdb files to the path, it is also important to add the symbols for the runtime library (the os).
http://msdn.microsoft.com/en-us/library/windows/hardware/ff565400(v=vs.85).aspx[^]