help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re: GUI closes without error message


From: Torsten Lilge
Subject: Re: Re: GUI closes without error message
Date: Tue, 23 Jun 2020 20:04:31 +0200

On Tue, 2020-06-23 at 13:03 -0400, John W. Eaton wrote:
> On 6/23/20 11:53 AM, Nicholas Jankowski wrote:
> >     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 have been able to use the following command at the Octave prompt on
> a 
> Windows system to start gdb in a separate command window and attach
> it 
> to the current Octave process:
> 
>    system (sprintf ("start gdb -p %d", getpid ()));
> 
> jwe

John, this command links gdb to the worker thread, right? Is there a
possibility to get the gui's pid from within octave?

Torsten
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]