From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: attach u/i oddity
Date: Tue, 11 Oct 2011 18:22:00 -0000 [thread overview]
Message-ID: <201110111922.17787.pedro@codesourcery.com> (raw)
In-Reply-To: <CADPb22SkyGbN+RjB8rdTg8JTq6D8PEE83aGCs7f4b5yQznrcGg@mail.gmail.com>
On Tuesday 11 October 2011 19:11:21, Doug Evans wrote:
> There was some cleverness that was wanted, was "tricky to get right
> right for remote targets.
You misunderstood. I meant the new warning I had suggested in the
same email I wrote that, the one where we'd check whether the loaded
file is the same that the target is reporting the process is
running is tricky on remote targets.
--
Pedro Alves
next prev parent reply other threads:[~2011-10-11 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 21:36 Doug Evans
2011-10-11 6:17 ` Joel Brobecker
2011-10-11 11:17 ` Pedro Alves
2011-10-11 16:46 ` Doug Evans
2011-10-11 17:20 ` Pedro Alves
2011-10-11 18:11 ` Doug Evans
2011-10-11 18:22 ` Pedro Alves [this message]
2011-10-11 18:56 ` Pedro Alves
2011-10-11 22:38 ` Doug Evans
2011-10-19 20:03 ` Tom Tromey
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=201110111922.17787.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
/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