From: Michael Welsh Duggan <mwd@cert.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: "4519@emacsbugs.donarmstrong.com" <4519@emacsbugs.donarmstrong.com>
Subject: bug#4519: 23.1.50; GDB MI problems: mi_cmd_stack_info_frame: No arguments required
Date: Wed, 23 Sep 2009 12:45:06 -0400 [thread overview]
Message-ID: <tntzl8lr4od.fsf@maru.green.cert.org> (raw)
In-Reply-To: <19129.65123.262702.16487@totara.tehura.co.nz> (Nick Roberts's message of "Wed, 23 Sep 2009 06:54:27 -0400")
Nick Roberts <nickrob@snap.net.nz> writes:
[...]
> Does the patch below fix the immediate problem?
It does. Thank you.
--
Michael Welsh Duggan
(mwd@cert.org)
next prev parent reply other threads:[~2009-09-23 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 14:38 bug#4519: 23.1.50; GDB MI problems: mi_cmd_stack_info_frame: No arguments required Michael Welsh Duggan
2009-09-23 10:54 ` Nick Roberts
2009-09-23 16:45 ` Michael Welsh Duggan [this message]
2009-09-23 23:25 ` Nick Roberts
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tntzl8lr4od.fsf@maru.green.cert.org \
--to=mwd@cert.org \
--cc=4519@emacsbugs.donarmstrong.com \
--cc=nickrob@snap.net.nz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).