From: Philipp Stephani <p.stephani2@gmail.com>
To: Jim Meyering <jim@meyering.net>, emacs-devel@gnu.org
Subject: Re: building/using address-sanitizer-enabled emacs?
Date: Tue, 09 May 2017 23:15:26 +0000 [thread overview]
Message-ID: <CAArVCkSdcREzueqHMcWB_xdXEsOT=LdB_pgPXGFOAYWtSpkRRw@mail.gmail.com> (raw)
In-Reply-To: <lubpf3o9v5mj1m.fsf@meyering.net>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
Jim Meyering <jim@meyering.net> schrieb am So., 7. Mai 2017 um 05:40 Uhr:
> Has anyone managed to dump an ASAN-enabled emacs recently?
> I can build and use an ASAN-enabled temacs, but it's too slow, of course.
I've just run the test suite through ASan with an undumped emacs on macOS.
I got lots of dynamic-stack-buffer-overflow errors when using SAFE_ALLOCA,
which I can't explain; maybe that's indeed an ASan bug because alloca isn't
that widely used.
There's one actual bug: the sockaddr_in in line 3538 of process.c needs to
be sockaddr_storage, otherwise it's too small for IPv6. (And
conv_sockaddr_to_lisp should probably check that the address is of the
expected length and not blindly overwrite the len argument.)
[-- Attachment #2: Type: text/html, Size: 1032 bytes --]
next prev parent reply other threads:[~2017-05-09 23:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 3:40 building/using address-sanitizer-enabled emacs? Jim Meyering
2017-05-07 19:54 ` Paul Eggert
2017-05-07 21:44 ` Jim Meyering
2017-05-08 2:36 ` Eli Zaretskii
2017-05-08 5:42 ` Paul Eggert
2017-05-08 14:39 ` Eli Zaretskii
2017-05-08 14:46 ` Paul Eggert
2017-05-08 16:04 ` Eli Zaretskii
2017-05-09 5:48 ` Jim Meyering
2017-05-09 15:18 ` Eli Zaretskii
2017-05-09 17:06 ` Jim Meyering
2017-05-09 17:45 ` Eli Zaretskii
2017-05-09 19:22 ` Paul Eggert
2017-05-09 22:49 ` Jim Meyering
2017-05-10 2:41 ` Eli Zaretskii
2017-05-16 21:49 ` Paul Eggert
2017-05-17 2:24 ` Eli Zaretskii
2017-05-17 14:46 ` Paul Eggert
2017-05-17 16:06 ` Eli Zaretskii
2017-05-17 20:05 ` Paul Eggert
2017-05-18 4:15 ` Eli Zaretskii
2017-05-09 23:15 ` Philipp Stephani [this message]
2017-05-10 2:42 ` Eli Zaretskii
2017-05-10 22:24 ` Philipp Stephani
2017-05-13 8:02 ` Eli Zaretskii
2017-05-13 15:08 ` [PATCH] Fix use of sockaddr_in Philipp Stephani
2017-05-13 16:52 ` Eli Zaretskii
2017-05-13 19:14 ` Andreas Schwab
2017-05-13 19:29 ` Eli Zaretskii
2017-05-13 20:05 ` Andreas Schwab
2017-05-14 2:32 ` Eli Zaretskii
2017-05-14 6:11 ` Andreas Schwab
2017-05-14 14:20 ` Eli Zaretskii
2017-05-15 6:15 ` Paul Eggert
2017-05-15 9:04 ` Philipp Stephani
2017-05-17 20:38 ` Paul Eggert
2017-05-27 11:35 ` Philipp Stephani
2017-05-17 15:16 ` Eli Zaretskii
2017-05-17 20:15 ` Paul Eggert
2017-05-14 10:28 ` Lars Ingebrigtsen
2017-05-14 19:06 ` Philipp Stephani
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='CAArVCkSdcREzueqHMcWB_xdXEsOT=LdB_pgPXGFOAYWtSpkRRw@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
/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).