From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch 2/3] attach-fail-reasons: Say more than ptrace: Operation not permitted.
Date: Wed, 14 Mar 2012 15:12:00 -0000 [thread overview]
Message-ID: <87obrzdxoy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120313135457.GA8363@host2.jankratochvil.net> (Jan Kratochvil's message of "Tue, 13 Mar 2012 14:54:57 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> Offtopic here but I think this code was another argument for C++,
Jan> wasn't it?
Yeah; but my sense was there was also general agreement that, even if we
switch gdb, we won't switch gdbserver.
Tom
prev parent reply other threads:[~2012-03-14 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 6:17 Jan Kratochvil
2012-03-08 13:55 ` Pedro Alves
2012-03-13 9:43 ` Jan Kratochvil
2012-03-13 10:33 ` Pedro Alves
2012-03-13 13:55 ` Jan Kratochvil
2012-03-13 14:35 ` Pedro Alves
2012-03-13 14:50 ` Jan Kratochvil
2012-03-13 15:03 ` [commit] " Jan Kratochvil
2012-03-14 15:12 ` Tom Tromey [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=87obrzdxoy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@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