From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: tsgates <tsgatesv@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Dumb idea on git library for script languages
Date: Mon, 28 Apr 2008 11:28:48 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0804281125330.5399@eeepc-johanness> (raw)
In-Reply-To: <1209366216.17090.4.camel@prosumer>
Hi,
On Mon, 28 Apr 2008, tsgates wrote:
> malloc_hook( size ) {
> void * rtn = malloc( size )
> if ( rtn ) {
> add_to_mem_record( thread_id, rtn )
> }
> }
>
> free_hook( ptr ) {
> if ( free( ptr ) ) {
> del_mem_record( thread_id, ptr )
> }
> }
>
> clean_mem() {
> for_each ( mem_records )
> free( ptr )
> }
This is not enough. We have quite some static variables which point
directly or indirectly to these allocated regions.
I think you'd need to implement some resetter functions if you were to
libify libgit.a. The easier way would definitely be to go with
libgit-thin, as Jakub suggested.
Ciao,
Dscho
next prev parent reply other threads:[~2008-04-28 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 7:03 Dumb idea on git library for script languages tsgates
2008-04-28 7:31 ` Jakub Narebski
2008-04-28 10:28 ` Johannes Schindelin [this message]
2008-04-29 4:06 ` Eric Hanchrow
2008-04-29 4:25 ` Govind Salinas
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=alpine.DEB.1.00.0804281125330.5399@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tsgatesv@gmail.com \
/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