public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: insight@sources.redhat.com
Subject: Insight does nothing but popup "crash" windows
Date: Thu, 28 Nov 2002 16:04:00 -0000	[thread overview]
Message-ID: <20021128190400.A24975@disaster.jaj.com> (raw)


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

             reply	other threads:[~2002-11-29  0:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 16:04 Phil Edwards [this message]
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
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=20021128190400.A24975@disaster.jaj.com \
    --to=phil@jaj.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).