Re: [PATCH] selftests: do not macro-expand failed assertion expressions

2018-12-10 Thread shuah
On 12/10/18 10:30 AM, Kees Cook wrote: On Sun, Dec 9, 2018 at 3:00 PM Dmitry V. Levin wrote: I've stumbled over the current macro-expand behaviour of the test harness: $ gcc -Wall -xc - <<'__EOF__' TEST(macro) { int status = 0; ASSERT_TRUE(WIFSIGNALED(status)); } TEST_HARNES

Re: [PATCH] selftests: do not macro-expand failed assertion expressions

2018-12-10 Thread Kees Cook
On Sun, Dec 9, 2018 at 3:00 PM Dmitry V. Levin wrote: > > I've stumbled over the current macro-expand behaviour of the test > harness: > > $ gcc -Wall -xc - <<'__EOF__' > TEST(macro) { > int status = 0; > ASSERT_TRUE(WIFSIGNALED(status)); > } > TEST_HARNESS_MAIN > __EOF__ > $ ./a.o

[PATCH] selftests: do not macro-expand failed assertion expressions

2018-12-09 Thread Dmitry V. Levin
I've stumbled over the current macro-expand behaviour of the test harness: $ gcc -Wall -xc - <<'__EOF__' TEST(macro) { int status = 0; ASSERT_TRUE(WIFSIGNALED(status)); } TEST_HARNESS_MAIN __EOF__ $ ./a.out [==] Running 1 tests from 1 test cases. [ RUN ] global.macro :