all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Andreas Schwab <schwab@suse.de>,
	Chip Coldwell <coldwell@redhat.com>,
	rms@gnu.org, emacs-devel@gnu.org
Subject: Re: dumping bug explained?
Date: Mon, 21 May 2007 09:40:24 -0700	[thread overview]
Message-ID: <4651CB78.2040402@redhat.com> (raw)
In-Reply-To: <87lkfikzpt.fsf@stupidchicken.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chong Yidong wrote:
> Do you know if Emacs will still need to be patched after these changes
> to glibc are done?

Not all the symptoms described in the bug can be explained by the
changes.  It might very well be that changes are needed.

In general, the use of malloc in emacs is horrific.  We are now going to
work around some of problems created by the changes when it comes to
assumptions emacs makes, but there is no guarantee that we can keep this up.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGUct42ijCOnn/RHQRAnuXAKChmJ9SwrUbeQeTmXNwwUB1RNI4ggCgxyNJ
zyTm12a0Glz8SK3Fs5/0qQU=
=DUhM
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2007-05-21 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 10:33 dumping bug explained? Richard Stallman
2007-05-21 10:53 ` Andreas Schwab
2007-05-21 14:15   ` Chong Yidong
2007-05-21 14:19     ` Chip Coldwell
2007-05-21 14:39       ` Chong Yidong
2007-05-21 14:52         ` Chip Coldwell
2007-05-21 16:40         ` Ulrich Drepper [this message]
2007-05-21 17:20           ` Chip Coldwell
2007-05-22 14:51           ` Richard Stallman

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=4651CB78.2040402@redhat.com \
    --to=drepper@redhat.com \
    --cc=coldwell@redhat.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=jakub@redhat.com \
    --cc=rms@gnu.org \
    --cc=schwab@suse.de \
    /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.