Insight does nothing but popup "crash" windows

Insight does nothing but popup "crash" windows

[Phil Edwards]

I find myself needing to debug a program, and it's just too complicated
for the character-based GDB, so I built CVS GDB with the gui enabled.

Initially it failed to run the program because the target was not valid.
After I figured out that I needed to set the target to "exec" myself,
and did that, the weirdness began.

I clicked on a call in main() to set a breakpoint.  Clicked "Run".  "Run"
pops up a window asking if I want to quit this debugging session.  I click
"No".  It pops up another window asking if I want to create a core file
of GDB.  I click "No".  It goes back to waiting for input.

Doesn't proceed with the program.  Doesn't move the current-source-line
highlighting.  Doesn't do anything.  Clicking "Next" or "Step" or, in fact,
any button at all, just pops up those two windows.


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

Re: Insight does nothing but popup "crash" windows

[Andrew Cagney]

> I find myself needing to debug a program, and it's just too complicated
> for the character-based GDB, so I built CVS GDB with the gui enabled.
> 
> Initially it failed to run the program because the target was not valid.
> After I figured out that I needed to set the target to "exec" myself,
> and did that, the weirdness began.
> 
> I clicked on a call in main() to set a breakpoint.  Clicked "Run".  "Run"
> pops up a window asking if I want to quit this debugging session.  I click
> "No".  It pops up another window asking if I want to create a core file
> of GDB.  I click "No".  It goes back to waiting for input.

Did the word `internal-error' appear anywhere in that text?  Hmm, lets try:
	(gdb) maint internal-error
in the console window and see what happens.  Er, no message :-(  Oops!

Bug.

Until that bug is fixed, suggest keeping a console open.

> Doesn't proceed with the program.  Doesn't move the current-source-line
> highlighting.  Doesn't do anything.  Clicking "Next" or "Step" or, in fact,
> any button at all, just pops up those two windows.

Anyway, does you insight source code base contain:

2002-11-27  Andrew Cagney  <cagney@redhat.com>

         * generic/gdbtk-stack.c (get_frame_name): Use get_frame_type
         instead of deprecated_frame_in_dummy.
         * generic/gdbtk-cmds.c (gdb_loc): Ditto.

?

Andrew

Re: Insight does nothing but popup "crash" windows

[Phil Edwards]

On Thu, Nov 28, 2002 at 09:48:14PM -0500, Andrew Cagney wrote:
> > Doesn't proceed with the program.  Doesn't move the current-source-line
> > highlighting.  Doesn't do anything.  Clicking "Next" or "Step" or, in fact,
> > any button at all, just pops up those two windows.
> 
> Anyway, does you insight source code base contain:
> 
> 2002-11-27  Andrew Cagney  <cagney@redhat.com>
> 
>          * generic/gdbtk-stack.c (get_frame_name): Use get_frame_type
>          instead of deprecated_frame_in_dummy.
>          * generic/gdbtk-cmds.c (gdb_loc): Ditto.
> 
> ?

Yes.

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

Re: Insight does nothing but popup "crash" windows

[Martin M. Hunt]

On Thu, 2002-11-28 at 16:04, Phil Edwards wrote:
> 
> I find myself needing to debug a program, and it's just too complicated
> for the character-based GDB, so I built CVS GDB with the gui enabled.
> 
> Initially it failed to run the program because the target was not valid.
> After I figured out that I needed to set the target to "exec" myself,
> and did that, the weirdness began.

Can you provide us any clues here?  What target?  What OS?  What do you
mean by "the target was not valid"? What exactly did you do?  Can you
start debugging your program using just GDB?

Martin

Re: Insight does nothing but popup "crash" windows

[Phil Edwards]

On Mon, Dec 09, 2002 at 10:50:14AM -0800, Martin M. Hunt wrote:
> On Thu, 2002-11-28 at 16:04, Phil Edwards wrote:
> > 
> > I find myself needing to debug a program, and it's just too complicated
> > for the character-based GDB, so I built CVS GDB with the gui enabled.
> > 
> > Initially it failed to run the program because the target was not valid.
> > After I figured out that I needed to set the target to "exec" myself,
> > and did that, the weirdness began.
> 
> Can you provide us any clues here?  What target?  What OS?

A program compiled for native i686/Linux, nothing special.


> What do you
> mean by "the target was not valid"?

The first time I tried to debug it, that's what GDB/Insight told me.
After poking about in the menus I found that the default seems to be for
some kind of remote debugging.  I changed the target from a blank selection
to "Exec" on a guess, and then it worked.

> What exactly did you do? 

"gdb -w ./a.cout core"

> Can you
> start debugging your program using just GDB?

Yes, but it quickly becomes incomprehensible.  Stepping through the
iostreams hierarchy calls without, for example, a seperate stack window,
is almost hopeless.


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

Re: Insight does nothing but popup "crash" windows

[Martin M. Hunt]

On Mon, 2002-12-09 at 12:27, Phil Edwards wrote:
> On Mon, Dec 09, 2002 at 10:50:14AM -0800, Martin M. Hunt wrote:
> > On Thu, 2002-11-28 at 16:04, Phil Edwards wrote:
> > > 
> > > I find myself needing to debug a program, and it's just too complicated
> > > for the character-based GDB, so I built CVS GDB with the gui enabled.
> > > 
> > > Initially it failed to run the program because the target was not valid.
> > > After I figured out that I needed to set the target to "exec" myself,
> > > and did that, the weirdness began.
> > 
> > Can you provide us any clues here?  What target?  What OS?
> 
> A program compiled for native i686/Linux, nothing special.
> 
> 
> > What do you
> > mean by "the target was not valid"?
> 
> The first time I tried to debug it, that's what GDB/Insight told me.
> After poking about in the menus I found that the default seems to be for
> some kind of remote debugging.  I changed the target from a blank selection
> to "Exec" on a guess, and then it worked.
> 
> > What exactly did you do? 
> 
> "gdb -w ./a.cout core"
> 

You are debugging a core file.  You cannot execute a core file, just
inspect its state.  Why did you try to set the target , set a breakpoint
and run?  Insight (and GDB) cannot do this.  Perhaps Insight should be
more intelligent, prevent this, display some useful help, etc.

Once you start Insight with the core file, just open a stack window,
register window, etc.  You can browse the stack and stack variables.

Martin

Re: Insight does nothing but popup "crash" windows

[Phil Edwards]

On Mon, Dec 09, 2002 at 01:01:12PM -0800, Martin M. Hunt wrote:
> > "gdb -w ./a.cout core"
> > 
> 
> You are debugging a core file.

Agh, ignore the "core" there.  That was a thinko.  (That's what I'm
/currently/ doing in another window.)

The problems with target, etc, were just "gdb -w ./a.out".


Phil (not as stupid as I appear *grin*)

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002