From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Rob Quill <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Light Formal Methods in GDB
Date: Thu, 12 Oct 2006 19:48:00 -0000 [thread overview]
Message-ID: <1160682474.14535.188.camel@localhost.localdomain> (raw)
In-Reply-To: <baf6008d0610120707n5e41bce0xce7f875db66a0afa@mail.gmail.com>
On Thu, 2006-10-12 at 15:07 +0100, Rob Quill wrote:
> Hi,
>
> What I am aiming to do is allow the programmer to debug his program
> using linear temporal logic formulas to verify sections of code and
> check that specified properties hold.
>
> I consider this important to be included in a debugger as it allows
> the programmer to stop the program execution at a certain point, and
> check at run-time that parts (or all) of the program are formally
> correct.
>
> An example would be the Until operator, which allows the programmer to
> specify that expression A must be true until expression B is true.
>
> I know this is a brief explanation, and if it unclear please feel free
> to ask me more about it, but I just wanted to see what people think of
> the idea.
Well, gdb can answer questions such as "is expression A true?",
but only in the context of a specific, static point in the
execution. And gdb doesn't know anything about formal or temporal
logic. Those are way outside its scope.
Are you thinking in terms of, say, a pre-processor that could
come up with a set of properties or propositions, translate them
into language that gdb can understand (eg. "stop here, and see if
expression A is true"), write the results to a file, and then
have a post-processor go over the results and test them against
the logical propositions?
next prev parent reply other threads:[~2006-10-12 19:48 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 [this message]
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
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=1160682474.14535.188.camel@localhost.localdomain \
--to=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