Re: Hanging conftest

[Pádraig Brady]

On 12/04/2013 03:38 AM, Pádraig Brady wrote:
> Unfortunately I'm seeing cores with this.
> 
> #0  0x000000375ce35215 in raise       () from /lib64/libc.so.6
> #1  0x000000375ce36b2b in abort       () from /lib64/libc.so.6
> #2  0x000000375ce78550 in malloc_printerr () from /lib64/libc.so.6
> #3  0x000000375ce79fc0 in _int_malloc () from /lib64/libc.so.6
> #4  0x000000375ce7a836 in malloc_check () from /lib64/libc.so.6
> #5  0x000000375ce7d4bf in calloc () from /lib64/libc.so.6
> #6  0x000000375cebb6b4 in re_acquire_state_context () from /lib64/libc.so.6
> #7  0x000000375cec1e6a in re_search_internal ()       from /lib64/libc.so.6
> #8  0x000000375cec64ac in re_search_stub () from /lib64/libc.so.6
> #9  0x000000375cec6eb8 in re_search () from /lib64/libc.so.6
> #10 0x000000000040081c in main () at t.c:84
> 
> Ah so mallopt(M_CHECK_ACTION, 2) is documented to abort() on error.
> I suppose we need to suppress core dumps now with the gnulib
> ]GL_NOCRASH[ ... nocrash_init() guard?
> Actually no, that doesn't catch SIGABRT.
> So I suppose you need an explicitly exit(1) in a SIGABRT
> signal handler in this test?

I installed the attached to convert the SIGABRT to a SIGTERM,
since _exit(1) wouldn't be distinguishable from the result |= 1 failure.

thanks,
Pádraig.

regex-nocoredump.patch
Description: Text Data