Click here to Skip to main content
11,415,164 members (75,276 online)
Rate this: bad
good
Please Sign up or sign in to vote.
See more: VC8.0 C++ Windbg
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 11:58am
Edited 22-Aug-12 21:44pm
v5
Comments
Shaunak De at 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.
Rate this: bad
good
Please Sign up or sign in to vote.

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.
  Permalink  
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 2

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[^]
  Permalink  

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

  Print Answers RSS
0 Sergey Alexandrovich Kryukov 9,200
1 OriginalGriff 7,512
2 Maciej Los 3,710
3 Abhinav S 3,298
4 Peter Leow 3,084


Advertise | Privacy | Mobile
Web02 | 2.8.150427.4 | Last Updated 29 Dec 2012
Copyright © CodeProject, 1999-2015
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100