gnu gcc sanitizer undefined behaviour runtime error messages
Reported by
vitti...@gmail.com,
Apr 24 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Steps to reproduce the problem: 1. Build chromium with gnu gcc/g++ -fsanitize=undefined 2. Run chrome 3. What is the expected behavior? There should be no runtime error: messages from the gnu gcc sanitizer What went wrong? I got many sanitizer runtime error messages at build time and at run time. The attached file undefined-build is a script of the build process with many 'runtime error:' messages from the gnu gcc sanitizer. The attached file undefined-chrome is the same when running chrome. Did this work before? N/A Chrome version: 58.0.3029.81 Channel: n/a OS Version: Fedora 25 Flash Version: Shockwave Flash 25.0 r0 chrome failed: FATAL:task_queue_impl.h(76)] Check failed: sequence_num != other.sequence_num (2 vs. 2) but I think the runtime errors should still be investigated
,
Apr 24 2017
Should I do anything to clarify this issue?
,
Apr 24 2017
Thanks for the report. Assigning to altimin@ based on code search, who made latest modifications in task_queue_impl.h
,
Apr 28 2017
Thank you for the report! I'm the one to help with failing DCHECKs in task_queue_impl.h, but other issues need a further triage. vitti570@, could you tell what exactly do you do to repro the issue? In particular, what sites are you visiting?
,
Apr 29 2017
The fatal error occurs on chromium initialization, no site or page visited yet. To reproduce it you must build with gnu gcc 6.3.0. To reproduce the undefined behaviour and its messages "runtime error:" need to build with -fsanitize=undefined -fno-omit-frame-pointer -g options.
,
May 18 2017
vitti570@ Are you still seeing this issue in latest stable - 58.0.3029.110 ?
,
May 18 2017
I'll check tomorrow.
,
May 22 2017
I downloaded version 60.0.3106.0 Building chrome with gnu gcc and option -fsanitize=undefined and then executing it I get the attached typescript (with script command). chrome fails with the following message FATAL:task_queue_impl.h(75)] Check failed: sequence_num != other.sequence_num (2 vs. 2) Now building chrome 58.0.3029.110.
,
Aug 10 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7ced8b65a703a9c28f0365c1aa27402812116c2e commit 7ced8b65a703a9c28f0365c1aa27402812116c2e Author: Alexander Timin <altimin@chromium.org> Date: Thu Aug 10 11:14:40 2017 [scheduler] Do not dcheck that compared wakeups are different in GCC. GCC can add additional comparisons to some stl structures, leading to an element being compared against itself. BUG=714530, 725882 R=skyostil@chromium.org Change-Id: If35b33d92636fc0e9759a0eee33ab0477d4c6425 Reviewed-on: https://chromium-review.googlesource.com/605767 Reviewed-by: Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#493355} [modify] https://crrev.com/7ced8b65a703a9c28f0365c1aa27402812116c2e/third_party/WebKit/Source/platform/scheduler/base/task_queue_impl.h
,
Aug 10 2017
,
Aug 10 2017
Sorry, I've fixed the task_queue_impl.h check failure. The rest of sanitizer warnings still need to be looked into.
,
Aug 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ranjitkan@chromium.org
, Apr 24 2017