public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug sanitizer/67308] New: FATAL: ThreadSanitizer: unexpected memory mapping
@ 2015-08-21 14:45 doko at gcc dot gnu.org
2015-08-22 14:35 ` [Bug sanitizer/67308] " jeromerobert at gmx dot com
2015-10-02 20:06 ` jeromerobert at gmx dot com
0 siblings, 2 replies; 3+ messages in thread
From: doko at gcc dot gnu.org @ 2015-08-21 14:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308
Bug ID: 67308
Summary: FATAL: ThreadSanitizer: unexpected memory mapping
Product: gcc
Version: 5.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Target Milestone: ---
[forwarded from https://bugs.debian.org/796246]
seen on the gcc-5-branch.
$ uname -r
4.1.0-3-generic
$ echo 'void main(void){}' | gcc -pie -fPIE -fsanitize=thread -xc - -ltsan &&
./a.out
FATAL: ThreadSanitizer: unexpected memory mapping 0x555caf24a000-0x555caf24b000
"""
There was an intentional change in the kernel that causes PIEs to be
loaded in a different address range:
https://git.kernel.org/linus/d1fd836dcf00d2028c700c7e44d2c23404062c90
I think ThreadSanitizer is just going to have to learn about this.
"""
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug sanitizer/67308] FATAL: ThreadSanitizer: unexpected memory mapping
2015-08-21 14:45 [Bug sanitizer/67308] New: FATAL: ThreadSanitizer: unexpected memory mapping doko at gcc dot gnu.org
@ 2015-08-22 14:35 ` jeromerobert at gmx dot com
2015-10-02 20:06 ` jeromerobert at gmx dot com
1 sibling, 0 replies; 3+ messages in thread
From: jeromerobert at gmx dot com @ 2015-08-22 14:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308
Jerome Robert <jeromerobert at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeromerobert at gmx dot com
--- Comment #1 from Jerome Robert <jeromerobert at gmx dot com> ---
Reported on the ThreadSanitizer bugtracker:
https://code.google.com/p/thread-sanitizer/issues/detail?id=96
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug sanitizer/67308] FATAL: ThreadSanitizer: unexpected memory mapping
2015-08-21 14:45 [Bug sanitizer/67308] New: FATAL: ThreadSanitizer: unexpected memory mapping doko at gcc dot gnu.org
2015-08-22 14:35 ` [Bug sanitizer/67308] " jeromerobert at gmx dot com
@ 2015-10-02 20:06 ` jeromerobert at gmx dot com
1 sibling, 0 replies; 3+ messages in thread
From: jeromerobert at gmx dot com @ 2015-10-02 20:06 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308
--- Comment #2 from Jerome Robert <jeromerobert at gmx dot com> ---
ThreadSanitizer moved to github so the bug is now:
https://github.com/google/sanitizers/issues/503
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-10-02 20:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-21 14:45 [Bug sanitizer/67308] New: FATAL: ThreadSanitizer: unexpected memory mapping doko at gcc dot gnu.org
2015-08-22 14:35 ` [Bug sanitizer/67308] " jeromerobert at gmx dot com
2015-10-02 20:06 ` jeromerobert at gmx dot com
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).