From: Phil Edwards <phil@jaj.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: Insight does nothing but popup "crash" windows
Date: Sun, 08 Dec 2002 15:48:00 -0000 [thread overview]
Message-ID: <20021208184848.A29844@disaster.jaj.com> (raw)
In-Reply-To: <3DE6D56E.3040900@redhat.com>; from ac131313@redhat.com on Thu, Nov 28, 2002 at 09:48:14PM -0500
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
next prev parent reply other threads:[~2002-12-08 23: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
2002-12-08 15:48 ` Phil Edwards [this message]
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=20021208184848.A29844@disaster.jaj.com \
--to=phil@jaj.com \
--cc=ac131313@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).