Bug 1258096 - ThreadSanitizer crash on kernel 4.x
ThreadSanitizer crash on kernel 4.x
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-28 21:42 EDT by husthl
Modified: 2017-08-08 08:10 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-08 08:10:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
test program (282 bytes, text/x-csrc)
2016-07-02 10:15 EDT, Gert Vervoort
no flags Details

  None (edit)
Description husthl 2015-08-28 21:42:17 EDT
Description of problem:
compile my program on GCC -fsanitize=thread, programe crash and report:
FATAL: ThreadSanitizer: unexpected memory mapping 0x564c51d39000-0x564c52938000

use old kernel core is ok.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 Marek Polacek 2015-08-31 03:39:28 EDT
Without a testcase there's nothing we can do. 
See <https://gcc.gnu.org/bugs/>.
Comment 2 Jan Kurik 2016-02-24 08:41:17 EST
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
Comment 3 Gert Vervoort 2016-07-02 10:15 EDT
Created attachment 1175346 [details]
test program

Example from http://illinois-cs.github.io/tsan

[gert@jupiter tmp]$ gcc -fsanitize=thread -pie -fPIC simple_race.c
[gert@jupiter tmp]$ ./a.out 
FATAL: ThreadSanitizer: unexpected memory mapping 0x55ad10dab000-0x55ad10dac000
[gert@jupiter tmp]$
Comment 4 Fedora End Of Life 2017-07-25 15:12:38 EDT
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2017-08-08 08:10:55 EDT
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.