From: Jim Blandy <jimb@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: remove meaningless code in ppc-bdm.c
Date: Tue, 11 May 2004 06:13:00 -0000 [thread overview]
Message-ID: <vt24qqntrt4.fsf@zenia.home> (raw)
In-Reply-To: <20040510223831.4cddda8a@saguaro>
Kevin Buettner <kevinb@redhat.com> writes:
> On 10 May 2004 17:45:17 -0500
> Jim Blandy <jimb@redhat.com> wrote:
>
> > I was going through this trying to keep it up to date with the
> > register numbering changes I was making, but then I realized it was
> > complete jibberish. First, the register contents are binary data; you
> > can't strcat them. Second, you can't strcat them into a fixed-size
> > buffer that is already filled with non-zero bytes.
> >
> > 2004-05-10 Jim Blandy <jimb@redhat.com>
> >
> > * ppc-bdm.c (bdm_ppc_fetch_registers): Replace utterly broken code
> > with a call to internal_error.
>
> Okay.
Committed, thanks.
prev parent reply other threads:[~2004-05-11 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vt2pt9bvr42.fsf@zenia.home>
2004-05-11 5:38 ` Kevin Buettner
2004-05-11 6:13 ` Jim Blandy [this message]
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=vt24qqntrt4.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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