all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Dave Abrahams <dave@boostpro.com>
Cc: 10656@debbugs.gnu.org
Subject: bug#10656: Duplicate large block deallocation
Date: Tue, 31 Jan 2012 10:30:40 -0800	[thread overview]
Message-ID: <4F283350.1080500@cs.ucla.edu> (raw)
In-Reply-To: <m2pqe0dj4q.fsf@pluto.luannocracy.com>

On 01/31/2012 06:47 AM, Dave Abrahams wrote:
> I've been using builds from http://emacsformacosx.com/builds; it's
>    just easier than building my own.

Can you check the source code from that location, and look for
the string "Duplicate large block deallocation"?  That string
is not in the Emacs source code itself, but it is in the Boehm
GC.  The string has to be coming from *somewhere*; perhaps it's
an auxiliary library that is in that location.

I agree that it's implausible that the Boehm GC would be run
as a default sort of build; it's just that I don't see how the
Emacs source code itself could be doing this.





  reply	other threads:[~2012-01-31 18:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 16:30 bug#10656: 24.0.92; Duplicate large block deallocation Dave Abrahams
2012-01-31  6:14 ` bug#10656: " Paul Eggert
2012-01-31 14:47   ` Dave Abrahams
2012-01-31 18:30     ` Paul Eggert [this message]
2012-01-31 18:50       ` Dave Abrahams
2012-01-31 18:59         ` Glenn Morris
2012-01-31 19:04           ` Dave Abrahams
2012-01-31 23:20             ` Paul Eggert
2012-02-01 15:04               ` Richard Stallman
2012-02-01 18:11                 ` Paul Eggert
2012-02-02  2:00                   ` bug#10656: emacsformacosx.com & the GPL David Caldwell
2012-02-02  2:38                     ` Paul Eggert
2012-02-02 13:26                     ` Richard Stallman
2012-01-31 18:50       ` bug#10656: Duplicate large block deallocation Dave Abrahams

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=4F283350.1080500@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=10656@debbugs.gnu.org \
    --cc=dave@boostpro.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.