From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
jan.kratochvil@redhat.com, pedro@codesourcery.com,
gdb-patches@sourceware.org
Subject: Re: [0/9]#2 Fix lost siginfo_t
Date: Tue, 31 Aug 2010 15:58:00 -0000 [thread overview]
Message-ID: <20100831155807.GJ2986@adacore.com> (raw)
In-Reply-To: <AANLkTinn-iqu_2E9FCHL0qUziX868rk0HnjrOwcYC+fe@mail.gmail.com>
> > I fear that it's time for another rewrite of linux-nat.c.
>
> For reference sake,
> I think such a rewrite wouldn't go far enough.
FWIW, If that helps simplifying the code, I am all for it too.
But I also agree with your assessement. The "target-specific"
IWBN if the gdbserver -low files and the gdb -nat files were
merged, one day.
--
Joel
next prev parent reply other threads:[~2010-08-31 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 7:10 Jan Kratochvil
2010-08-30 19:50 ` Pedro Alves
2010-08-30 20:11 ` Jan Kratochvil
2010-08-30 20:49 ` Mark Kettenis
2010-08-30 21:13 ` Jan Kratochvil
2010-08-31 7:26 ` Doug Evans
2010-08-31 15:58 ` Joel Brobecker [this message]
2010-08-31 10:46 ` Pedro Alves
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=20100831155807.GJ2986@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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