From: Phil Edwards <phil@jaj.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight does nothing but popup "crash" windows
Date: Mon, 09 Dec 2002 12:28:00 -0000 [thread overview]
Message-ID: <20021209152759.A5986@disaster.jaj.com> (raw)
In-Reply-To: <1039459815.1145.2.camel@Dragon>; from hunt@redhat.com on Mon, Dec 09, 2002 at 10:50:14AM -0800
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
next prev parent reply other threads:[~2002-12-09 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 16:04 Phil Edwards
2002-11-28 18:48 ` Andrew Cagney
2002-12-08 15:48 ` Phil Edwards
2002-12-09 10:47 ` Martin M. Hunt
2002-12-09 12:28 ` Phil Edwards [this message]
2002-12-09 12:58 ` Martin M. Hunt
2002-12-09 13:00 ` Phil Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021209152759.A5986@disaster.jaj.com \
--to=phil@jaj.com \
--cc=hunt@redhat.com \
--cc=insight@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).