unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
* bug#10588: failed build with --enable-debug-malloc
       [not found] <CAO0=bvvtoBNPj=q0_J=1u1XznovirFubGosbU4zf31Q+VVrZZA@mail.gmail.com>
@ 2012-01-23 20:58 ` Andy Wingo
  2012-02-05 15:03   ` Andy Wingo
  0 siblings, 1 reply; 2+ messages in thread
From: Andy Wingo @ 2012-01-23 20:58 UTC (permalink / raw)
  To: erana Owl; +Cc: 10588

On Sun 22 Jan 2012 21:57, erana Owl <0wl256@gmail.com> writes:

> running configure with --enable-debug-malloc fails on snarfing .doc

Redirecting to bug-guile to create a new ticket.

Thanks for the report,

Andy
-- 
http://wingolog.org/





^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#10588: failed build with --enable-debug-malloc
  2012-01-23 20:58 ` bug#10588: failed build with --enable-debug-malloc Andy Wingo
@ 2012-02-05 15:03   ` Andy Wingo
  0 siblings, 0 replies; 2+ messages in thread
From: Andy Wingo @ 2012-02-05 15:03 UTC (permalink / raw)
  To: erana Owl; +Cc: 10588-done

On Mon 23 Jan 2012 21:58, Andy Wingo <wingo@pobox.com> writes:

> On Sun 22 Jan 2012 21:57, erana Owl <0wl256@gmail.com> writes:
>
>> running configure with --enable-debug-malloc fails on snarfing .doc

I "fixed" this.  Guile itself no longer registers GC-controlled
mallocations, as since 2.0 it is no longer necessary (nor advised) to
call scm_gc_free, so you don't get the pairing that you need to track
numbers of live objects.

We should probably remove the debug-malloc code entirely, given that it
doesn't map well to the current API.

Andy
-- 
http://wingolog.org/





^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-02-05 15:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAO0=bvvtoBNPj=q0_J=1u1XznovirFubGosbU4zf31Q+VVrZZA@mail.gmail.com>
2012-01-23 20:58 ` bug#10588: failed build with --enable-debug-malloc Andy Wingo
2012-02-05 15:03   ` Andy Wingo

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 read-only IMAP folder(s) and NNTP newsgroup(s).