Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Rob Quill" <rob.quill@gmail.com>
To: "Michael Snyder" <Michael.Snyder@palmsource.com>, gdb@sourceware.org
Subject: Re: YACC/Lex
Date: Mon, 09 Oct 2006 20:09:00 -0000	[thread overview]
Message-ID: <baf6008d0610091309w58df9877k67c4e8c8231bd842@mail.gmail.com> (raw)
In-Reply-To: <1160417660.14535.33.camel@localhost.localdomain>

Thanks for your help with this and my previous email. I'm not going to
be using to parse anything so difficult as a whole language. I just
need it to parse some LTL formulae. The basic aim for what I am trying
to do is allow GDB to do some relatively simple model checking, which
assuming I can get it working efficiently should make debugging quite
a bit easier as the programmer can just check the properties of small
sections of code to see that they hold, and it means that, as it is
integrated into GDB, there is no need for a seperate tool for formal
verification.

Would I be right in saying that it wouldn't be OK to mix O'Caml and C
for GDB? (I'm almost certain I am, bt correct me if I'm not)

Thanks,
Rob

On 09/10/06, Michael Snyder <Michael.Snyder@palmsource.com> wrote:
> On Mon, 2006-10-09 at 12:44 +0100, Rob Quill wrote:
> > Hi,
> >
> > Is it ok to use code generated by YACC and/or Lex in GDB? If not, what
> > alternatives are there?
>
> First of all, the open source / gnu / fsf equivalents are byacc (bison),
> and flex.  Bison and byacc are two independent implementations of a
> yacc equivalent.  If I remember correctly, gdb will work with bison but
> prefers byacc.  I'm not sure if it will work with yacc itself any more.
>
> If you cd to the gdb source directory and do "ls *.y", you will see
> that there are existing (b)yacc parsers for ada, c, java, fortran,
> pascal and modula-2, plus a few more.  There's also a separate lexer
> for ada, ada-lex.l.
>
> Look at the makefile to see how these get built, and then if you want to
> pursue it further, look at language.c and language.h.
>
> Michael
>
>


      reply	other threads:[~2006-10-09 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09 11:45 YACC/Lex Rob Quill
2006-10-09 12:33 ` YACC/Lex Daniel Jacobowitz
2006-10-09 18:14 ` YACC/Lex Michael Snyder
2006-10-09 20:09   ` Rob Quill [this message]

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=baf6008d0610091309w58df9877k67c4e8c8231bd842@mail.gmail.com \
    --to=rob.quill@gmail.com \
    --cc=Michael.Snyder@palmsource.com \
    --cc=gdb@sourceware.org \
    /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