From: Andrew Cagney <ac131313@cygnus.com>
To: law@redhat.com, GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: gdb-patches Digest 11 Feb 2001 23:49:53 -0000 Issue 545
Date: Fri, 16 Feb 2001 10:59:00 -0000 [thread overview]
Message-ID: <3A8D777D.6730FE39@cygnus.com> (raw)
In-Reply-To: <6986.982345742@slagheap.cygnus.com>
Jeffrey A Law wrote:
> > 2001-02-11 Paul Hilfinger <hilfingr@nile.gnat.com>
> >
> > * hpux-thread.c (save_inferior_pid): Change call to make_cleanup
> > to make arguments conform.
> > (restore_inferior_pid): Change signature to that expected by
> > make_cleanup.
> No comment on this one -- I'm not that familiar with the new guidelines
> for make_cleanup. I'll let Andrew comment on this.
It was rejected. It was hiding a type compatibility problem by simply
casting it.
> > 2001-02-11 Paul Hilfinger <hilfingr@lisbon.int.act-europe.fr>
> >
> > * hpux-thread.c (hpux_thread_xfer_memory): Add mem_attrib
> > argument to parameter list and to call in order to conform to
> > to_xfer_memory field of struct target_ops.
> ?!? I can't see how this can be right.
>
> >From target.h in the current CVS tree the to_xfer_memory signature looks
> like this:
>
> int (*to_xfer_memory) PARAMS ((CORE_ADDR memaddr, char *myaddr,
> int len, int write,
> struct target_ops * target));
int (*to_xfer_memory) (CORE_ADDR memaddr, char *myaddr,
int len, int write,
struct mem_attrib *attrib,
struct target_ops *target);
I think it is an obvious fix - I just need to cross check the change
with another target. I was hopeing J.T. would get to it before I did.
Andrew
next parent reply other threads:[~2001-02-16 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6986.982345742@slagheap.cygnus.com>
2001-02-16 10:59 ` Andrew Cagney [this message]
2001-02-16 10:10 Michael Elizabeth Chastain
2001-02-16 10:20 ` Jeffrey A Law
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=3A8D777D.6730FE39@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=law@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