Re: GUI closes without error message

[Markus Mützel]

Am 23. Juni 2020 um 17:53 Uhr schrieb "Nicholas Jankowski":
> > Can you attach gdb to the PID of the running Octave process and try if it 
> > catches any exception? In case it does: What is the backtrace of the error?
> 
> Do we have instructions for doing that on a Windows install without 
> rebuilding? Is that possible? I believe there was recently another email 
> chain about needing to build a Windows version that still had the debug 
> symbols for gdb?

I was afraid that something like this would be what stayed from that other 
thread.
Let me try to be as clear as possible about this: It is *not* necessary to 
rebuild Octave to be able to attach gdb to it.
In fact, Octave for Windows already comes with a complete msys2 environment 
including a working gdb out of the box.

I never understood why the guy from that other thread insisted on re-compiling 
Octave for Windows. I tried to make that point repeatedly but it looks like it 
never came across.

The biggest difference is maybe that the backtrace references the mangled 
function names (without any source file line numbers). But such backtraces can 
give a good idea where a crash is occurring many times anyway.

HTH,
Markus