all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 18885@debbugs.gnu.org
Subject: bug#18885: 25.0.50; build fails with ASan enabled
Date: Wed, 29 Oct 2014 17:04:44 +0100	[thread overview]
Message-ID: <mvma94elv4z.fsf@hawking.suse.de> (raw)
In-Reply-To: <87r3xqevui.fsf@udel.edu> (Mark Oteiza's message of "Wed, 29 Oct 2014 11:31:17 -0400")

Mark Oteiza <mvoteiza@udel.edu> writes:

> Hi,
>
> For debugging another project, I resorted to using gcc's address
> sanitizer to help track down a bug, and it actually helped find others
> along the way.  I came across a crash in emacs and decided to build
> trunk with the address sanitizer enabled.
>
> The build failed with this output on Arch Linux.  The build config is
> the same as below except without optimization and with
> -fsanitize=address in CFLAGS and LDFLAGS.
>
> Loading /tmp/makepkg/emacs-git/src/emacs/lisp/tooltip.el (source)...
> Finding pointers to doc strings...
> Finding pointers to doc strings...done
> Dumping under the name emacs
> =================================================================
> ==6778==ERROR: AddressSanitizer: global-buffer-overflow on address 0x000000cf9d70 at pc 0x7ffff6f2fd1a bp 0x7fffffffc6a0 sp 0x7fffffffbe48
> READ of size 3601184 at 0x000000cf9d70 thread T0
>     #0 0x7ffff6f2fd19 in __interceptor_memcpy.part.38 (/usr/lib/libasan.so.1+0x2fd19)
>     #1 0x91421d in unexec /tmp/makepkg/emacs-git/src/emacs/src/unexelf.c:1060

This is expected.  unexec and asan are not compatible.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."





      reply	other threads:[~2014-10-29 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 15:31 bug#18885: 25.0.50; build fails with ASan enabled Mark Oteiza
2014-10-29 16:04 ` Andreas Schwab [this message]

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=mvma94elv4z.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=18885@debbugs.gnu.org \
    --cc=mvoteiza@udel.edu \
    /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.