This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Debugger freeze problem when you specify program on thecommand line
- From: Keith Seitz <keiths at redhat dot com>
- To: Al Leitch <opcodeac at hotmail dot com>
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: 30 Jun 2003 11:19:40 -0700
- Subject: Re: Debugger freeze problem when you specify program on thecommand line
- Organization:
- References: <Law14-F53YrfTUvk1vP00021989@hotmail.com>
On Mon, 2003-06-30 at 01:52, Al Leitch wrote:
> Thankfully there's a nice but slightly inconvient workaround for this,
> anyway... If you run insight and specify on the command line, a program to
> debug, it works all and well. The problems begin when you "hit" the run
> button. Then the whole debugger and program apparently freezes. Even if
> you simply press the "nexti" button, the freeze will happen.
>
There should be no difference between specifying a program name on the
command line (which is what I do 99% of the time) and using a menu or
shortcut.
Next time you try this, double-check the target settings (File->Target
Settings...), keep a console window open (View->Console), and keep a
debug window open. That should let you know if there are any
errors/warnings that you might be missing.
To open a debug window, enter "tk ManagedWin::open DebugWin" at the
console prompt.
Keith