Stack trace in Windows

[V Stuart Foote]

So having a bit of a chore when grabbing a stack trace in Windows.

Application to use seems to be the Sysinternals (Microsoft TechNet)
Russinovich & Cogswell developed Process Monitor utility.  It will
completely capture to log ALL system activity on a Windows OS.

The problem then becomes filtering the log to identify the faulting
component.

Looking at the current TinberBox 6 crasher  fdo#63680
<https://bugs.freedesktop.org/show_bug.cgi?id=63680>   for Tinderbox builds
left me scratching my head looking for the exact point where Writer
aborts--and LibreOffice starts a recovery.

Can someone give me a hint about the process flow of session recovery and
which LibreOffice .dll would I look for to see the catch of the Writer crash
and launch a recovery? Trying to pin that down, so I can work backwards
through the dump.

  



--
View this message in context: http://nabble.documentfoundation.org/Stack-trace-in-Windows-tp4051411.html
Sent from the Dev mailing list archive at Nabble.com.