unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Paul Eggert" <eggert@cs.ucla.edu>, "Jan Synáček" <jsynacek@redhat.com>
Cc: 23726@debbugs.gnu.org
Subject: bug#23726: emacs 25.0.94 crashes
Date: Wed, 8 Jun 2016 20:34:58 +0200	[thread overview]
Message-ID: <72a0452f-b732-d562-47a7-cedbc9548a39@redhat.com> (raw)
In-Reply-To: <489b54c6-1d39-4f47-9c35-36eea32c7b6c@cs.ucla.edu>

On 06/08/2016 07:32 PM, Paul Eggert wrote:
> Has Rawhide incorporated some of Florian Weimer's malloc patches? If so,
> this is almost surely causing the problem. I will CC: Florian to give
> him a heads-up. See:
>
> https://sourceware.org/ml/libc-alpha/2016-06/msg00211.html

That's not the patch, it's not even in upstream master.  If that patch 
was in, you wouldn't see the problem anymore because Emacs' internal 
malloc would be used.

The problem is that the realloc implementation for dumped chunks is 
incorrect; that bit is already in glibc master and rawhide.  I think I 
can see what is wrong: The size computation for the old chunk size in 
realloc is wrong, and the trailing sizeof (size_t) bytes are not copied. 
  Fortunately, it's not a conceptual problem with the heap rewriter.

> I am surprised that you can use valgrind.

The valgrind failure is typical of what you get with a dumped Emacs. 
valgrind intercepts realloc and returns 0 because an off-heap pointer is 
detected.

Florian






  reply	other threads:[~2016-06-08 18:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 10:21 bug#23726: 25.0.94; emacs 25.0.94 crashes Jan Synáček
2016-06-08 16:49 ` Eli Zaretskii
2016-06-08 17:32 ` bug#23726: " Paul Eggert
2016-06-08 18:34   ` Florian Weimer [this message]
2016-06-08 18:52     ` Florian Weimer
2016-06-08 18:57       ` Paul Eggert
2016-06-09  6:17       ` Jan Synacek

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72a0452f-b732-d562-47a7-cedbc9548a39@redhat.com \
    --to=fweimer@redhat.com \
    --cc=23726@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=jsynacek@redhat.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 public inbox

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

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).