Bug 2055187

Summary: test_leaksan.c test case from upstream integration test suite fails on aarch64, no leaks found
Product: Red Hat Enterprise Linux 8 Reporter: Miloš Prchlík <mprchlik>
Component: clangAssignee: Tom Stellard <tstellar>
Status: CLOSED WONTFIX QA Contact: Jesus Checa <jchecahi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.8CC: jchecahi, mprchlik, sipoyare
Target Milestone: rcKeywords: Bugfix, Triaged
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2093385 (view as bug list) Environment:
Last Closed: 2023-08-16 07:28:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2093385, 2140677    

Description Miloš Prchlík 2022-02-16 12:51:07 UTC 
Description of problem:

$ cat test_leaksan.c
// Test asan use after free
//
// REQUIRES: clang
// RUN: %clang -o %t -fsanitize=address -g %s
// RUN: env ASAN_OPTIONS="log_path=stdout:exitcode=0"  %t 2>&1 > %t.out
// RUN: grep -q "detected memory leaks" %t.out

#include <stdlib.h>

void *p;

int main() {
  p = malloc(7);
  p = 0; // The memory is leaked here.
  return 0;
}
$ 
$ /usr/bin/clang -o test_leaksan.c.tmp -fsanitize=address -g test_leaksan.c
$ env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp 2>&1 > test_leaksan.c.tmp.out
$ grep -q "detected memory leaks" test_leaksan.c.tmp.out
$ cat test_leaksan.c.tmp.out 
$ 


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

clang-13.0.1-1.module+el8.6.0+14118+d530a951.aarch64
llvm-13.0.1-1.module+el8.6.0+14118+d530a951.aarch64
glibc-2.28-189.el8.aarch64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Tom Stellard 2023-01-30 21:25:38 UTC 
*** Bug 2140677 has been marked as a duplicate of this bug. ***
Comment 5 RHEL Program Management 2023-08-16 07:28:34 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.