Bug 103053 - AddressSanitizer: heap-use-after-free in test compiler_subgroup_media_block_read_us2
Summary: AddressSanitizer: heap-use-after-free in test compiler_subgroup_media_block_r...
Status: RESOLVED MOVED
Alias: None
Product: Beignet
Classification: Unclassified
Component: Beignet (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Zhigang Gong
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-01 13:48 UTC by Alexis Engelke
Modified: 2018-10-12 21:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Test and ASan output (23.03 KB, text/plain)
2017-10-01 13:48 UTC, Alexis Engelke 		Details
View All

Description Alexis Engelke 2017-10-01 13:48:57 UTC 
Created attachment 134595 [details]
Test and ASan output

AddressSanitizer detects a heap-use-after-free in gbe::ir::Immediate::getIntegerValue() const when compiling latest master and running the test compiler_subgroup_media_block_read_us2, see the attached log.

Compilation command:
(Remove '-Wl,--no-undefined' from CMakeLists.txt)
$ cmake -G Ninja -DENABLE_OPENCL_20=false -DCOMPILER=CLANG -DCMAKE_C_FLAGS="-fsanitize=address -fno-omit-frame-pointer" -DCMAKE_CXX_FLAGS="-fsanitize=address -fno-omit-frame-pointer" -DCMAKE_SHARED_LINKER_FLAGS="-fsanitize=address" -DCMAKE_BUILD_TYPE=Debug ..
$ env ASAN_OPTIONS=alloc_dealloc_mismatch=0:detect_leaks=false ninja
$ env ASAN_OPTIONS=alloc_dealloc_mismatch=0:detect_leaks=false ninja utest

System: Fedora 26, Kernel 4.12.13-300.fc26, LLVM 4.0.1
Comment 1 GitLab Migration User 2018-10-12 21:24:45 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/beignet/beignet/issues/35.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.