From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: kaszian@informatik.uni-bonn.de, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [bap] BAP Tools with Python Bindings
Date: Wed, 18 Mar 2015 10:42:27 -0400 [thread overview]
Message-ID: <CAK7rcp8R4SXOHG-nnXx-MWNWxWbPp9+O1tCSsoHQa7eDC33CJA@mail.gmail.com> (raw)
In-Reply-To: <9696c69210215810aca6ca5f0c54be9f.squirrel@webmail.iai.uni-bonn.de>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Depends on what version of BAP you're using. That I know of, the toil
binary and iltrans that were available previously now no longer are,
although the functionality that you're looking for still exists.
Can you tell me what it is that you want to do?
(Also, as you can see, BAP mailing list is retired, please use Caml-list,
because, well, BAP is in ocaml :) )
On Tue, Mar 17, 2015 at 11:25 AM, Viktor Kaszian <
kaszian@informatik.uni-bonn.de> wrote:
> Dear Everyone,
>
> I am currently working on a project dealing with C disassembly and I want
> to use BAP as a base framework, since it has Python Bindings. I've read
> through the BAP Handbook, and since i would like to make extensive use of
> the tools described in Chapter Two (toil, iltrans) I was wondering:
>
> How do I use them with the Python Bindings? I have already loaded a binary
> and played around a bit, but is there a guide to using the tools properly?
>
>
> Best Regards,
> Viktor
>
> _______________________________________________
> BAP-Users mailing list
> BAP-Users@lists.andrew.cmu.edu
> https://lists.andrew.cmu.edu/mailman/listinfo/bap-users
>
[-- Attachment #2: Type: text/html, Size: 1685 bytes --]
next parent reply other threads:[~2015-03-18 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9696c69210215810aca6ca5f0c54be9f.squirrel@webmail.iai.uni-bonn.de>
2015-03-18 14:42 ` Kenneth Adam Miller [this message]
2015-03-18 14:46 ` Anil Madhavapeddy
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=CAK7rcp8R4SXOHG-nnXx-MWNWxWbPp9+O1tCSsoHQa7eDC33CJA@mail.gmail.com \
--to=kennethadammiller@gmail.com \
--cc=caml-list@inria.fr \
--cc=kaszian@informatik.uni-bonn.de \
/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