Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com, Dodji Seketeli <dseketel@redhat.com>
Subject: Re: [patch] MI: breakpoint "script" is a LIST
Date: Thu, 13 Nov 2008 15:39:00 -0000	[thread overview]
Message-ID: <20081113134113.GA15321@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <gfh94m$e85$1@ger.gmane.org>

On Thu, 13 Nov 2008 14:12:54 +0100, Vladimir Prus wrote:
> Jan Kratochvil wrote:
> > 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?

The current code does not comply to any generic MI parser as it violates the
MI grammar http://sourceware.org/gdb/current/onlinedocs/gdb_26.html#SEC264 ,
as pointed out by Dodji.

It may be compliant only to some hacky buggy parsers written specifically for
each MI command.

If we want to keep -break-list "script" to produce tuples we have to change it
from current
  script={"silent","return"}
to some
  script={line0="silent",line1="return"}
which will IMO also break any existing buggy parsers.

And GDB is now between major releases 6.8->6.9 which IMO means it does not
have to keep bug-to-bug compatibility.


Regards,
Jan


  reply	other threads:[~2008-11-13 13:42 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
2008-11-13 15:39   ` Jan Kratochvil [this message]
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=20081113134113.GA15321@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dseketel@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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