From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org
Subject: Re: attach u/i oddity
Date: Tue, 11 Oct 2011 06:17:00 -0000 [thread overview]
Message-ID: <20111011061636.GR3802@adacore.com> (raw)
In-Reply-To: <CADPb22QEk4VA45fi338xPVevDnp8fKbsPWKGH4E9iZLwYrBSyw@mail.gmail.com>
> The user never specified forever.x32 as the program to debug, gdb was
> being clever. However, if it's going to be clever the first time,
> it's a bug (from the user's perspective) to not be clever the second
> time too (IMO).
I agree. I was surprised by the reported behavior.
--
Joel
next prev parent reply other threads:[~2011-10-11 6:17 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 [this message]
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
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=20111011061636.GR3802@adacore.com \
--to=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