RE: Re: GUI closes without error message

[Michael Holme Sørensen]

Thanks for all your inputs. I have started the gdb as proposed based on the small guideline from Nicholas. Please let me know how to pull out a report from this when I experience the failure next time.

 

Thanks, Michael

 

Michael Holme Sørensen
Development Engineer, Motor design | Global R&D

Asetek
Assensvej 2, 9220 Aalborg East, Denmark
www.asetek.com
Mobile +45 25 66 68 54
Office +45 96 45 30 60 Ext. 360

From: Nicholas Jankowski <jankowskin@asme.org>
Sent: 23. juni 2020 22:21
To: Markus Mützel <markus.muetzel@gmx.de>
Cc: Nicholas Jankowski <jankowskin@asme.org>; Torsten Lilge <ttl-octave@mailbox.org>; John W. Eaton <jwe@octave.org>; Michael Holme Sørensen <mso@asetek.com>; help-octave@gnu.org
Subject: Re: Re: GUI closes without error message

 

 

On Tue, Jun 23, 2020 at 3:25 PM Markus Mützel <markus.muetzel@gmx.de> wrote:

Am 23. Juni 2020 um 21:17 Uhr schrieb "Nicholas Jankowski":
> running John's command, however, does lock the main octave program until you quit from adb, though, so i'm not sure if there's another way to call it that it will catch an exception that crashes octave.

That is the expected behavior when gdb attaches to a process. At that point, you would e.g. be able to add breakpoints if you needed to.
When you are ready continue executing the process with the command "continue" (or just "c") at the gdb prompt.
After that the gdb prompt seems "unresponsive" because execution returned to Octave.

 

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?

 

 

Caution: This email originated from outside Asetek. Do not click links, open attachments or forward unless you recognize the sender and know the content is safe.