Do you mean something more than gdb? I've used gdb and I get the
following stack trace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1075667072 (LWP 9819)]
0x0805a026 in caml_oldify_mopup ()
(gdb) bt
#0  0x0805a026 in caml_oldify_mopup ()
#1  0x0805a0e5 in caml_empty_minor_heap ()
#2  0x0805a190 in caml_minor_collection ()
#3  0x0805a21a in caml_check_urgent_gc ()
#4  0x0805ac3f in caml_alloc_string ()
#5  0x0805e138 in caml_create_string ()
#6  0x080688de in caml_interprete ()
#7  0x08059be9 in caml_main ()
#8  0x08059d60 in main ()
(gdb)

I'm not sure where to go from here. What do you recommend?

Thanks

Lex

On Sat, 18 Dec 2004, Damien Doligez wrote:

> On 17 déc. 2004, at 07:44, Christopher Alexander Stein wrote:
>
> > Hi, I am getting an exception Out_of_memory. The manual tells me
> > this is raised by the garbage collector when there is
> > insufficient memory to complete the computation. Is there any way
> > to find out what is causing this; what is gobbling up memory too
> > fast for the GC? Perhaps there is a way to get and analyze a core
> > file or a way to catch the exception and dump the heap and
> > garbage collector state. Any suggestions?
>
> Have you tried using the debugger?
>
> -- Damien
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>