From: "Yaron M. Minsky" <yminsky@CS.Cornell.EDU>
To: Erik Arneson <erik@aarg.net>, caml-list@inria.fr
Subject: Re: [Caml-list] Debugging mixed ocaml/C code
Date: Wed, 18 Sep 2002 15:45:24 -0400 [thread overview]
Message-ID: <3D88D7D4.3050805@cs.cornell.edu> (raw)
In-Reply-To: <15744.40944.948274.528474@monkey.x.aarg.net>
It took me a while, but I just posted a version of my Berkeley DB
wrapper. Here's the URL:
http://minsky-primus.homeip.net/ocaml/bdb.tar.gz
There are currently problems with the transactional support (it
segfaults and I don't know why), but other than that seems to work
pretty well. There is currently good-but-not-complete support for
dbenvs, dbs, cursors and transactions.
y
Erik Arneson wrote:
> On 11 Sep 02, Yaron M. Minsky <yminsky@CS.Cornell.EDU> wrote:
>
>>Does anyone have any suggestions for debugging mixed ocaml/C code? I
>>have some code that uses a wrapper for the Berkeley DB.
>
>
> Yaron,
>
> I unfortunately don't have any debugging hints for you, but I'm
> interested in hearing more about your BerkeleyDB module. Do you need
> any help with it? Will it be available to the public when you're
> done? I have some projects coming up that will need BerkeleyDB
> access, and I've been putting them off because I didn't feel like
> writing an OCaml interface, but I would be more than happy to help you
> out!
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2002-09-18 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 2:15 Yaron M. Minsky
2002-09-12 10:09 ` Olivier Andrieu
[not found] ` <15744.40944.948274.528474@monkey.x.aarg.net>
2002-09-12 17:31 ` Yaron M. Minsky
2002-09-18 19:45 ` Yaron M. Minsky [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=3D88D7D4.3050805@cs.cornell.edu \
--to=yminsky@cs.cornell.edu \
--cc=caml-list@inria.fr \
--cc=erik@aarg.net \
/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