Amended Re: X11 stability with insight & gdb

Amended Re: X11 stability with insight & gdb

[John Mills]

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.

X11 stability with insight & gdb

[John Mills]

Hello -

This is my first post to this list, so please redirect me if it's not a 
good forum for my question.

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.

When I run 'gdb' from 'emacs' ('gud' wrapper), it all works fine: I can
start, stop, restart, or kill by program from the 'gbd' window. (In that 
setting the 'gdb' window is also the program's console window - which 
may be significant here.)

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.

Any suggestions on dealing with my X11 session crashes?

Thanks.

 - John Mills
   john.m.mills@alum.mit.edu

Re: Amended Re: X11 stability with insight & gdb

[Keith Seitz]

John Mills wrote:
> 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?

If your program uses stdio and you're on a unix machine, you can use the 
  target settings dialog to select "use xterm as inferior's tty".

One note about this, though: you MUST use the Run button to start your 
application. There is still a huge disconnect between Insight's GUI and 
GDB's internals, so you cannot use the console window and type "run" to 
get this to work.

Keith

Re: Amended Re: X11 stability with insight & gdb

[John Mills]

Keith -

Thanks, especially for the GDB vs. INSIGHT caution. I'll play with that
setting; even now I can use S-N and GDB together. I appreciate S-N's
source-tree analysis but am otherwise OK using emacs w/ gdb.

 - John

On Fri, 26 Oct 2007, Keith Seitz wrote:

> John Mills wrote:
> > 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?
> 
> If your program uses stdio and you're on a unix machine, you can use the 
>   target settings dialog to select "use xterm as inferior's tty".
> 
> One note about this, though: you MUST use the Run button to start your 
> application. There is still a huge disconnect between Insight's GUI and 
> GDB's internals, so you cannot use the console window and type "run" to 
> get this to work.
> 
> Keith