Archives of the Caml mailing list > Message from David MENTRE

Browse thread

Re: [Caml-list] Native compiler support for m68k?

Xavier Leroy
- Richard Zidlicky
  - Byron Hale
  - Benjamin Geer
  - David MENTRE
  - Damien Doligez
    - Christophe Raffalli
      - Pierre Weis
        
        Christophe Raffalli
      - Xavier Leroy
- Gleb N. Semenov
  - Xavier Leroy
    - Daniel M. Albro
- Richard Zidlicky
  - Xavier Leroy
- Richard Zidlicky

Date:	-- (:)
From:	David MENTRE <dmentre@l...>
Subject:	Re: [Caml-list] Native compiler support for m68k?

Richard Zidlicky <rz@linux-m68k.org> writes:

> What could be the source of such indeterministic behaviour?
> gc?

I would guess it is related to GC or bad memory allocation (in case of C
code).

As far as I remember, OCaml GC is using usual libc malloc and free, so
you could activate libc checks to help find the bug (see mcheck(), there
is also an environment variable I don't remember). You could also take a
look at libefence.

Other things that might help is to zeroing data structures before
releasing them to free(). Sometimes, you reuse a datastructure that is
has been freed.

To make the port, what have you modified? Only Caml code or also C code?

My .2 euros,
Yours,
d.
-- 
 David Mentré <dmentre@linux-france.org>
   http://www.linux-france.org/~dmentre/david-mentre-public-key.asc
 GnuPG key fingerprint: A7CD 7357 3EC4 1163 745B  7FD3 FB3E AD7C 2A18 BE9E

-------------------
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