Version française
Home     About     Download     Resources     Contact us    
Browse thread
Calling C from OCaml, GC problems
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: David.Mentre@i...
Subject: Calling C from OCaml, GC problems
Hello all Camlists,

A friend of mine and me are trying to interface CMU bdd library (in C)
with OCaml. We have a rough code but a bug is still alive. I still have
some questions relative to OCaml and C interfacing:

 1. the ocaml doc (paragraph 15.5) states that CAMLparam and CAMLreturn
    macros should be used. However, example code in 15.7 does not use
    them (even if functions have value typed parameters). The Unix
    interfacing code ocaml-2.04/otherlibs/unix/) doesn't use those macro
    either. Faulty doc?  Are those macros not mandatory? What is the
    rationale?

 2. when compiling, I've tons of warning like this:
bdd_interface.c: In function `mlbdd_alloc_manager':
bdd_interface.c:136: warning: left-hand operand of comma expression has no effect
bdd_interface.c:136: warning: unused variable `caml__dummy_result'

    the corresponding C code is:
value mlbdd_alloc_manager(MANAGER m) {
        CAMLparam0();
        CAMLlocal1 (result);  

        bdd_overflow_closure(m, mlbdd_overflow, NULL);
        result = alloc_final(Size_ml_manager, mlbdd_free_manager, 0, 1);
        Manager_store_pointer(result, (value)m);
        PRINT_DEBUG("Alloc manager");
        CAMLreturn result;
}

    Did I use wrongly those CAML* macros?

 3. The code is running on small examples but segfault on bigger
    ones. From gdb backtrace, it seems clear that my bug is releated to
    a GC problem:
(gdb) bt
#0  0x8065c45 in mark_slice ()
#1  0x806607b in major_collection_slice ()
#2  0x8066663 in minor_collection ()
#3  0x80666ac in check_urgent_gc ()
#4  0x805ba53 in alloc_final ()
#5  0x804e0fc in mlbdd_alloc_vbdd (m=0x809f020, b=0x80f55b9) at bdd_interface.c:204
#6  0x804ec85 in mlbdd_or (vb1=717431320, vb2=717431288) at bdd_interface.c:441
#7  0x80645bb in interprete ()
#8  0x80656d3 in caml_main ()
#9  0x805b1d5 in main ()
#10 0x2ab457e2 in __libc_start_main () from /lib/libc.so.6

    The bdd library is using itself a memory management library calling
    sbrk(2). Can it trigger problems with OCaml GC (like the GC going
    into bdd structures)?

Below URL's to C and OCaml interface codes if somebody need them:
  http://www.irisa.fr/paris/pages-perso/David-Mentre/bdd.ml
  http://www.irisa.fr/paris/pages-perso/David-Mentre/bdd_interface.c


Many thanks in advance for any help.

best regards,
david
-- 
 David.Mentre@irisa.fr -- http://www.irisa.fr/prive/dmentre/
 Opinions expressed here are only mine.