Amended Re: X11 stability with insight & gdb

[John Mills <johnmills at speakeasy dot net>]

Hello -

I tried another approach and have more data.

If I start 'insight' or 'source-navigator' from a console (xterm)  
command and _don't_ start a separate console from 'insight' (yielding a
"read-only"  xterm it seems), then my original console stays 'live' and I
can run the application successfully and interrupt it either from the GUI 
or from the console.

Is there a way to have 'insight' start a "true" console window for my 
application, or is a foreground startup from a console command line the 
best way to debug a native app?

Thanks.

 - John Mills

On Fri, 26 Oct 2007, John Mills wrote:

 ...
> I'm starting 'insight' from 'source-navigator' as a 'gdb' front end, and 
> using it to debug a native, multi-thread console application that runs in 
> my Linux environment.
 
> Starting, running, and stepping through my application all work fine as
> far as I can see. When I try to _stop_ the running program with the
> run/stop icon, however, it crashes my X11 environment and ends my login
> session. When I try to stop the program from the 'gdb' window, I get a 
> 'Debugger busy' message and am ignored. When I try to stop the program 
> with a '^C' signal from insight's console window I am ignored.
 ...

 >>---> This may be the issue>>--->

> I start 'source-navigator' from a GUI launcher in X11, start 'insight' 
> from the 'Debugger' panel in 'source-navigator', and start 'gdb' as an 
> insight configuration setting.