Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Submitting patches to Ocaml
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2002-11-25 (10:11)
From: Xavier Leroy <xavier.leroy@i...>
Subject: Re: [Caml-list] Submitting patches to Ocaml
> I decided to run valgrind against the bytecode interpreter and it
> found a memory leak, which fixed.

Yes, valgrind is an excellent tool.  As for the memory leaks, there
are things that are not freed on exit (heap, stack), but that's
intentional (the OS is goign to free everything itself).  Bug reports
for other leaks are most welcome.

> Anyway, I have a patch for the memory leak and for a couple of
> other minor things I saw in the C code.
> What's the best way to get these into the CVS tree?  Should I
> send the patches to caml-bugs?

The best way is to submit bug reports to caml-bugs.  Attach a patch if
you wish, but that's optional (we may want to fix the bugs differently).
A patch without a bug report is useless.

> Regarding the bug tracker, I noticed that it doesn't do any
> tracking of the people that respond to or categorize bugs.
> It seems pretty feature short compared to Bugzilla.  Would
> there be any way to get Bugzilla installed at Inria?

Bugzilla has a reputation of being awfully hard to install.  Other bug
tracking systems are better alternatives.  Jitterbug (what we
currently use) is indeed simplistic, but fits our needs well.  

- Xavier Leroy
To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: