From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro@codesourcery.com>
Subject: Re: [patch 0/4] Fix hw watchpoints
Date: Tue, 18 Aug 2009 21:23:00 -0000 [thread overview]
Message-ID: <e394668d0908181345i41b31085rf9da1292c58ee933@mail.gmail.com> (raw)
In-Reply-To: <20090818163754.GA16719@host0.dyn.jankratochvil.net>
On Tue, Aug 18, 2009 at 9:37 AM, Jan
Kratochvil<jan.kratochvil@redhat.com> wrote:
> On Tue, 18 Aug 2009 18:24:00 +0200, Doug Evans wrote:
>> Have you looked at whether gdbserver has similar issues?
>
> No.
>
> http://sourceware.org/ml/archer/2009-q2/msg00084.html
> On Sun, 10 May 2009 17:42:48 +0200, Pedro Alves wrote:
> # On Sunday 10 May 2009 15:55:49, Jan Kratochvil wrote:
> # > May I ask why do you put effort both on linux-nat.c and gdbserver? Isn't it
> # > cheaper to unify the codebase and start (transparently) using gdbserver even
> # > for local operations?
> #
> # Probably, I think we're slowly going in that direction. Making the
> # debug interface control parts of gdbserver into a library and reuse
> # it from gdb for native debugging (code sharing, that is) as been
> # suggested many times.
>
> Expecting currently I should copy the changes also to gdb/gdbserver/ . Is it
> OK to first get them approved for linux-nat.c & co. ?
Ah, righto.
prev parent reply other threads:[~2009-08-18 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 19:45 Jan Kratochvil
2009-08-18 16:34 ` Doug Evans
2009-08-18 17:10 ` Jan Kratochvil
2009-08-18 21:23 ` Doug Evans [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=e394668d0908181345i41b31085rf9da1292c58ee933@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.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