caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Blair Zajac <blair@orcaware.com>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Submitting patches to Ocaml
Date: Mon, 25 Nov 2002 10:29:58 -0800	[thread overview]
Message-ID: <3DE26C26.EFB8043A@orcaware.com> (raw)
In-Reply-To: <20021125111155.A14115@pauillac.inria.fr>

Xavier Leroy wrote:
> 
> > 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.

Thanks.  Will do.

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

I've installed it several times on different sites and it wasn't
particularly hard.  And comparing it to writing a GC, it seems
simple :)  But it does take a while.

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
-------------------
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


  reply	other threads:[~2002-11-25 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23  0:17 Blair Zajac
2002-11-25 10:11 ` Xavier Leroy
2002-11-25 18:29   ` Blair Zajac [this message]
2002-11-26  6:44     ` Sven Luther
2002-11-26  6:59       ` Blair Zajac
2002-11-27 14:42   ` [Caml-list] Bugzilla installation (was Re: Submitting patches to Ocaml) Tim Freeman

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=3DE26C26.EFB8043A@orcaware.com \
    --to=blair@orcaware.com \
    --cc=caml-list@inria.fr \
    --cc=xavier.leroy@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).