From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Hui Zhu <teawater@gmail.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH/RFC] Move the cmdarg before load execarg
Date: Fri, 28 Jan 2011 12:25:00 -0000 [thread overview]
Message-ID: <m3ei7xgrdu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110128095213.GA18993@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Fri, 28 Jan 2011 10:52:13 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> It apparently breaks the much more common case of:
Jan> gdb program -ex 'b main'
FWIW, I think backward compatibility here is more important than whether
or not the options are defined in the best way possible. In this case
it is especially true, since there is a fairly reasonable workaround.
Tom
next prev parent reply other threads:[~2011-01-28 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 9:28 Hui Zhu
2011-01-28 9:58 ` Jan Kratochvil
2011-01-28 12:25 ` Tom Tromey [this message]
2011-01-30 0:52 ` Hui Zhu
2011-01-31 15:03 ` Jan Kratochvil
2011-02-08 13:39 ` Hui Zhu
2011-01-31 15:05 ` 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=m3ei7xgrdu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=teawater@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).