Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, of course you don't know because you don't have a minidump to look at. You should do the absolute minimum when the SetUnhandledExceptionFilter callback fires. The process is in a perilous state. It crashed. Locks might be held, the heap locks are particularly troublesome. You can't expect MiniDumpWriteDump() to succeed.</p> <p>What you need is a little guard process that waits on a named event. Start it up as early as possible in your main() function and pass it your process ID. The guard process waits on both that event and your process handle. In your exception callback, just signal the event and immediately sleep for a long time. That wakes up the guard process, it calls MiniDumpWriteDump() plus whatever else is necessary to let you know about the crash. And kills your main program.</p>
    singulars
    1. This table or related slice is empty.
    1. POVisual C++ program crashed, but no dumpfile generated. why?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USHans Passant
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't understand how `MiniDumpWriteDump` has any more of a chance to succeed when run from another process. If locks are held then those locks are held. It doesn't matter which process is trying to access the locked resource. Plus, since `MiniDumpWriteDump` is not thread-safe you are doomed either way. Unless you can synchronize all threads (which you cannot, since your program is in an indeterminate state) there is no guarantee for success. What you say sounds plausible, but doesn't provide a rationale of why the guard process will have a higher chance for success.
      singulars
      1. PO
      1. USIInspectable
    2. COThread-safety is of no concern, you only have one thread calling MiniDumpWriteDump(). Whether the process is so corrupted that basic calls like CreateFile() and HeapAlloc() that MDWD needs to get its job done can fail most certainly is a concern. It is a filter of sorts, if you do it in-process then you'll never get to see the really bad crashes that are impossible to debug. Good thing, perhaps.
      singulars
      1. PO
      1. USHans Passant
    3. COThanks for the response. Still not quite convinced here: If a process is so corrupted that `CreateFile` fails (correct me, but can it fail unless kernel memory is corrupted?) then you could also argue that `SetEvent` will. The same goes for `HeapAlloc` basically, unless it fails for OOM. I would assume that MDWD works on 'preallocated' static data, though - this would also explain why it is not thread-safe. On a less technical note, have you had a minidump generated out-of-context that an in-process solution would probably not have?
      singulars
      1. PO
      1. USIInspectable
 

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