[Bug malloc/16159] malloc_printerr() deadlock, when calling malloc_printerr() again

["eblake at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16159

Eric Blake <eblake at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eblake at redhat dot com

--- Comment #21 from Eric Blake <eblake at redhat dot com> ---
(In reply to Darryl Miles from comment #6)
> How do I stop this fancy backtrace stuff from working ?  I want to setup an
> environment variable to turn it off as a workaround ?

According to:
https://lists.gnu.org/archive/html/bug-gnulib/2013-11/msg00103.html
setting MALLOC_CHECK_=2 in the environment is sufficient to prevent the error
message attempts; but that sounds like something you set at program start
rather than something we can do via setenv() at the time of reporting the first
error (because setenv uses malloc).

> There is no need to actually fix the bug, you are over thinking the issue. 

Yes, there IS a need to fix something.  The link above points to a case of a
user that is unhappy that their ./configure failed because the conftest program
hung after tickling a malloc corruption bug in regex.  Configure should never
hang (thankfully, configure tests are one case where the MALLOC_CHECK_=2 trick
may be sufficient - someone probing for known glibc bugs doesn't care about a
bactrace, only about successful exit status).

-- 
You are receiving this mail because:
You are on the CC list for the bug.