HomePhabricator

[lldb] Fix Recognizer/assert.test with glibc-2.33.9000-31.fc35.x86_64

Authored by jankratochvil on Jul 1 2021, 12:14 AM.

Description

[lldb] Fix Recognizer/assert.test with glibc-2.33.9000-31.fc35.x86_64

While on regular Linux system (Fedora 34 GA, not updated):

  • thread #1, name = '1', stop reason = hit program assert frame #0: 0x00007ffff7e242a2 libc.so.6`raise + 322 frame #1: 0x00007ffff7e0d8a4 libc.so.6`abort + 278 frame #2: 0x00007ffff7e0d789 libc.so.6`assert_fail_base.cold + 15 frame #3: 0x00007ffff7e1ca16 libc.so.6`assert_fail + 70
    • frame #4: 0x00000000004011bd 1`main at assert.c:7:3

On Fedora 35 pre-release one gets:

  • thread #1, name = '1', stop reason = signal SIGABRT
    • frame #0: 0x00007ffff7e48ee3 libc.so.6`pthread_kill@GLIBC_2.2.5 + 67 frame #1: 0x00007ffff7dfb986 libc.so.6`raise + 22 frame #2: 0x00007ffff7de5806 libc.so.6`abort + 230 frame #3: 0x00007ffff7de571b libc.so.6`assert_fail_base.cold + 15 frame #4: 0x00007ffff7df4646 libc.so.6`assert_fail + 70 frame #5: 0x00000000004011bd 1`main at assert.c:7:3

I did not write a testcase as one needs the specific glibc. An
artificial test would just copy the changed source.

Reviewed By: mib

Differential Revision: https://reviews.llvm.org/D105133