Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Klee Dienes <klee@apple.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: ChangeLog typo?
Date: Tue, 05 Nov 2002 01:09:00 -0000	[thread overview]
Message-ID: <59FF17BA-F09E-11D6-9BFD-00039396EEB8@apple.com> (raw)

Fixed; thanks.

> Klee,
>
> I think there's a minor mistake in the following ChangeLog entry:
>
> 2002-10-11  Klee Dienes  <kdienes@apple.com>
>
>         * findvar.c (read_memory_typed_address): New function.
>         * gdbcore.h (read_memory_typed_address): Add prototype.
>         * blockframe.c (sigtramp_saved_pc): Use 
> read_memory_typed_address
> 	to read a value destined for a CORE_ADDR, not read_memory_integer.
>         * f-valprint.c (f77_get_dynamic_upperbound): Ditto.
>         (f77_get_dynamic_lowerbound): Ditto.
>
> read_memory_typed_address() is actually in corefile.c, not findvar.c.
>
> Kevin


             reply	other threads:[~2002-11-05  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  1:09 Klee Dienes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 15:15 Kevin Buettner

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=59FF17BA-F09E-11D6-9BFD-00039396EEB8@apple.com \
    --to=klee@apple.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