From: Pedro Alves <pedro@codesourcery.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Adjust insight to recent GDB changes around TARGET_OBJECT_MEMORY
Date: Tue, 30 Jun 2009 01:48:00 -0000 [thread overview]
Message-ID: <200906191454.13726.pedro@codesourcery.com> (raw)
In-Reply-To: <4A37FF33.50709@redhat.com>
On Tuesday 16 June 2009 21:23:15, Keith Seitz wrote:
> Pedro Alves wrote:
>
> > (I didn't find any other TARGET_OBJECT_MEMORY access under gdbtk)
> >
> > I'd check this in as obvious, but I don't know the rules on
> > this side of the fence. ;-)
>
> I think of it exactly the same way as gdb. By all means, if it is an
> "obvious" failure, don't hesitate to commit it.
Ack. Thanks.
> Thanks for the patch!
You're welcome. Checked in now.
--
Pedro Alves
prev parent reply other threads:[~2009-06-19 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 20:25 Pedro Alves
2009-06-19 13:53 ` Keith Seitz
2009-06-30 1:48 ` Pedro Alves [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=200906191454.13726.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=insight@sourceware.org \
--cc=keiths@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).