From: Daniel Jacobowitz <drow@false.org>
To: Rob Quill <rob.quill@gmail.com>
Cc: Michael Snyder <Michael.Snyder@palmsource.com>, gdb@sourceware.org
Subject: Re: Light Formal Methods in GDB
Date: Mon, 16 Oct 2006 14:38:00 -0000 [thread overview]
Message-ID: <20061016143758.GA20426@nevyn.them.org> (raw)
In-Reply-To: <baf6008d0610160318g476f2657y4e036f88cce80ff@mail.gmail.com>
On Mon, Oct 16, 2006 at 11:18:45AM +0100, Rob Quill wrote:
> Hi.
>
> Could you elaborate on this please. I am confused as to how I could
> use the GDB scripting language. Can I say things such as "if val = 1"
> then do some transition of the automaton and then single step the
> program? Or, say that I has somehow already figured out where I wanted
> the breakpoints to be I could just set GDB to break there, make
> automaton transitions and then keep going.
>
> Is that what you meant? Because that sounds excellent and a lot
> simpler than trying to build it into GDB some how, which was what I
> thought I would have to do.
I doubt that you could do it directly in GDB's scripting language;
although, it might be possible, with use of the "shell" builtin command
(to run another program to cause the automaton to transform).
However, it sounds to me like what you really want is an external
program in control of GDB. The only tricky part would be "handing
off" to the user once you've reached a state where the constraints
are violated, but I'm sure that you can find a way to do that.
The external program can initially drive GDB through the MI interface,
then switch interpreters to the CLI for the user.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-16 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 14:07 Rob Quill
2006-10-12 19:48 ` Michael Snyder
2006-10-13 10:04 ` Rob Quill
2006-10-13 18:47 ` Michael Snyder
2006-10-16 10:18 ` Rob Quill
2006-10-16 14:38 ` Daniel Jacobowitz [this message]
2006-10-16 18:22 ` Michael Snyder
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=20061016143758.GA20426@nevyn.them.org \
--to=drow@false.org \
--cc=Michael.Snyder@palmsource.com \
--cc=gdb@sourceware.org \
--cc=rob.quill@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