mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-06 11:41:34 +00:00
9d3d254a8b
The VG_(extend_stack) call needs to be properly guarded because the
passed-in address is not necessarily part of an extensible stack
segment. And an extensible stack segment is the only thing that
function should have to deal with.
Previously, the function VG_(am_addr_is_in_extensible_client_stack)
was introduced to guard VG_(extend_stack) but it was not added in all
places it should have been.
Also, extending the client stack during signal delivery (in sigframe-common.c)
was simply calling VG_(extend_stack) hoping it would do the right thing.
But that was not always the case. The new testcase
none/tests/linux/pthread-stack.c exercises this (3.10.1 errors out on it).
Renamed ML_(sf_extend_stack) to ML_(sf_maybe_extend_stack) and add
proper guard logic for VG_(extend_stack).
Testcases none/tests/{amd64|x86}-linux/bug345887.c by Ivo Raisr.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15138
10 lines
425 B
Plaintext
10 lines
425 B
Plaintext
|
|
Process terminating with default action of signal 11 (SIGSEGV)
|
|
Access not within mapped region at address 0x........
|
|
at 0x........: inner (bug345887.c:7)
|
|
If you believe this happened as a result of a stack
|
|
overflow in your program's main thread (unlikely but
|
|
possible), you can try to increase the size of the
|
|
main thread stack using the --main-stacksize= flag.
|
|
The main thread stack size used in this run was ....
|