From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [0/9]#2 Fix lost siginfo_t
Date: Mon, 30 Aug 2010 21:13:00 -0000 [thread overview]
Message-ID: <20100830211322.GA27931@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <201008302047.o7UKlPYR005898@glazunov.sibelius.xs4all.nl>
On Mon, 30 Aug 2010 22:47:25 +0200, Mark Kettenis wrote:
> That seems rather backwards. If gdbserver works so well, the
> linux-nat.c code should be able to work even better.
Just due to inevitable multi-host systems (read "cloud"; software is still
slower and GHz have their technological limit) the linux-nat.c model (=without
a wire protocol) is a history.
Thanks,
Jan
next prev parent reply other threads:[~2010-08-30 21:13 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 [this message]
2010-08-31 7:26 ` Doug Evans
2010-08-31 15:58 ` Joel Brobecker
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=20100830211322.GA27931@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--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