Re: GUI closes without error message

[Kai Torben Ohlhus]

On 6/24/20 5:20 AM, Nicholas Jankowski wrote:
> 
> ok, thanks.  maybe this is something we could detail over on the wiki? 
> I know there's a spot for collecting hard-to-troubleshoot windows crash
> issues here:
> https://wiki.octave.org/FAQ#MS_Windows
> 
> not sure if there's a better place for this. but for general clueless
> windows users like me, something including 
> 
> - the command to start adb
>  system (sprintf ("start gdb -p %d", getpid ())); 
> 
> - the way to get back to 'normal' octave operation
> 'continue'
> 
> - then run octave as normal to recreate the crash, and ....  what's
> next?  generate a report? it'll automatically generate one? do we need
> to run commands before 'continue' to tell it what/where to dump some
> output? 
> 
> - and what to send back to the help list to help developers troubleshoot? 
> 
> - if any of this falls under 'fails to start', can this be started from
> the CLI before launching Octave to capture the startup crash details?
>  

The help thread was successfully hijacked :D

@Nicholas: Maybe you can overhaul that wiki page [1] and link from [2]
to it.  It almost contains all the information given here.

Kai

[1] https://wiki.octave.org/Debugging_Octave
[2] https://wiki.octave.org/FAQ#MS_Windows