From: Blair Zajac <blair@orcaware.com>
To: Caml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] Submitting patches to Ocaml
Date: Fri, 22 Nov 2002 16:17:54 -0800 [thread overview]
Message-ID: <3DDEC932.6B3C74C@orcaware.com> (raw)
I decided to run valgrind against the bytecode interpreter and it
found a memory leak, which fixed.
By the way, valgrind is this really cool memory leak and access
detector for Linux. It doesn't require any modifications to any
binaries. See
http://developer.kde.org/~sewardj/
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?
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?
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
next reply other threads:[~2002-11-23 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 0:17 Blair Zajac [this message]
2002-11-25 10:11 ` Xavier Leroy
2002-11-25 18:29 ` Blair Zajac
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=3DDEC932.6B3C74C@orcaware.com \
--to=blair@orcaware.com \
--cc=caml-list@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).