From: Andrew Cagney <ac131313@redhat.com>
To: Phil Edwards <phil@jaj.com>
Cc: insight@sources.redhat.com
Subject: Re: Insight does nothing but popup "crash" windows
Date: Thu, 28 Nov 2002 18:48:00 -0000 [thread overview]
Message-ID: <3DE6D56E.3040900@redhat.com> (raw)
In-Reply-To: <20021128190400.A24975@disaster.jaj.com>
> 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
next prev parent reply other threads:[~2002-11-29 2:48 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 [this message]
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=3DE6D56E.3040900@redhat.com \
--to=ac131313@redhat.com \
--cc=insight@sources.redhat.com \
--cc=phil@jaj.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).