Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would attach WinDbg when the program is running and do a minidump when it debugbreaks on a crash or exception:</p> <pre><code>.dump /ma c:\mem.dmp // c:\mem.dmp could be any other location you desire </code></pre> <p>I would enable gflags for your app, either from the command line of within WinDbg:</p> <pre><code>!gflag +ust </code></pre> <p>remember to remove this flag after!!</p> <p>Then you could run an automated exepction analysis:</p> <pre><code>!analyze -v </code></pre> <p>this may tell you what it thinks caused the crash, you can dump the call stacks of all threads:</p> <pre><code>~* kb </code></pre> <p>and if see anything suspicuous you can switch thread and inspect further:</p> <pre><code>~x s </code></pre> <p>You can inspect the exception context record:</p> <pre><code>.ecxr </code></pre> <p>there is a good link on how to recover the call stack from a catch block:http://blogs.msdn.com/b/slavao/archive/2005/01/30/363428.aspx and also this: <a href="http://blogs.msdn.com/b/jmstall/archive/2005/01/18/355697.aspx" rel="nofollow">http://blogs.msdn.com/b/jmstall/archive/2005/01/18/355697.aspx</a></p> <p>the main thing here is that with windbg attached you should be able to inspect the state of all the threads and the call stacks, you can also open the minidump in visual studio: <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee416349%28v=vs.85%29.aspx#Analysis_of_a_minidump" rel="nofollow">http://msdn.microsoft.com/en-us/library/windows/desktop/ee416349%28v=vs.85%29.aspx#Analysis_of_a_minidump</a> if you prefer visual studio for navigating, you can open the same dump in windbg to use its tools for analysis and visual studio for navigating the code. Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to log or replay lines or instructions executed immediately before a crash
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USEdChum
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the elaborate answer, but analyzing the current state of the program is not the problem; I also know the call stack of the crashing thread. What I need is to know the execution history (without having to add trace statements everywhere in the program myself).
      singulars
      1. PO
      1. This table or related slice is empty.
    2. COwhat you are asking for is some way of logging the activity? You could set a breakpoint on your module or other modules and execute the `wt` command: `bp myDLL!myClass:someFunc() "wt;g;"` you could replace myDLL with a start address and similarly the same for `wt`, and write the output to a logfile: `.logopen c:\myLog.txt` but this would need some kind of precog of knowing where errors would occur, you could inject some logging using Logexts.dll but this limits it to MS API calls
      singulars
      1. PO
      1. USEdChum
    3. CO`wt` only logs the current thread; I am looking for a way to log all threads. Furthermore, I have noted that `wt` sometimes stops logging for no apparent reason.
      singulars
      1. PO
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload