From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] MI: breakpoint "script" is a LIST
Date: Thu, 13 Nov 2008 15:35:00 -0000 [thread overview]
Message-ID: <gfh94m$e85$1@ger.gmane.org> (raw)
In-Reply-To: <20081113130442.GA12991@host0.dyn.jankratochvil.net>
Jan Kratochvil wrote:
> Hi,
>
> Nemiver could not parse the MI2 output. The list of commands is a `list', not
> a `tuple'.
For how long this bug is here? Is the risk that existing frontend break higher than
inconvenience to keep the code as is?
- Volodya
next prev parent reply other threads:[~2008-11-13 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 15:11 Jan Kratochvil
2008-11-13 15:35 ` Vladimir Prus [this message]
2008-11-13 15:39 ` Jan Kratochvil
2008-11-13 20:21 ` Vladimir Prus
2008-11-13 21:35 ` Tom Tromey
2008-11-13 21:55 ` Marc Khouzam
2008-11-13 21:59 ` Jan Kratochvil
2008-11-16 8:23 ` André Pönitz
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='gfh94m$e85$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.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