Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
	gdb-patches@sources.redhat.com,
	        Dodji Seketeli <dseketel@redhat.com>
Subject: Re: [patch] MI: breakpoint "script" is a LIST
Date: Thu, 13 Nov 2008 21:59:00 -0000	[thread overview]
Message-ID: <20081113183937.GA20538@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA067CA4F1@ecamlmw720.eamcs.ericsson.se>

On Thu, 13 Nov 2008 19:33:22 +0100, Marc Khouzam wrote:
> > But I'm sure all existing frontends handle this. I don't think I'm gonna
> > test Eclipse (both CDI and DSF), and KDevelop (3.3 and 4), to make sure
> > the proposed change does not break them. So, we probably get to wait till
> > MI3.
> 
> What is this "script" thing?  I can't find it in the documentation.
> From a quick look to CDI and DSF, it is not being parsed.
> Probably because it is not in the doc :-)

GDB .tar.gz contains gdb/.gdbinit with:

b info_command
commands
	silent
	return
end

$ info '(gdb)Break Commands' 

If you run in the gdb/ directory:

$ ./gdb --interpreter=mi2 ./gdb
(gdb)
 -break-list
^done ...,script={"silent","return"},...

which should have been:
^done ...,script=["silent","return"],...


Regards,
Jan


  reply	other threads:[~2008-11-13 18:40 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
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 [this message]
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=20081113183937.GA20538@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dseketel@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=marc.khouzam@ericsson.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