[Bug malloc/19754] abort() of malloc/tst-malloc-thread-exit with corrupted thread stack when RLIMIT_AS is in force

[fweimer at redhat dot com]

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Nick Alcock from comment #2)
> Running with my recently-posted --enable-stack-protector=all does *not*
> trigger a stack-protection abort when this testcase abort()s, which suggests
> that whatever is going wrong when the stack is smashed

This is an explicit abort call because a thread creation fails.  The error
message clearly indicates that the process has run out of resources.  It is not
caused by any kind of memory corruption.

I don't think this is a bug in the test.  The test needs a few threads to
exercise the malloc implementation, and each thread has a certain address space
requirement.  If you constrain the environment too much, the test cannot run in
a meaningful way.

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