]> git.ipfire.org Git - thirdparty/gcc.git/commit - libbacktrace/unittest.c
[libbacktrace] Don't point to released memory in backtrace_vector_release
authorvries <vries@138bc75d-0d04-0410-961f-82ee72b054a4>
Tue, 27 Nov 2018 08:26:04 +0000 (08:26 +0000)
committervries <vries@138bc75d-0d04-0410-961f-82ee72b054a4>
Tue, 27 Nov 2018 08:26:04 +0000 (08:26 +0000)
commitcc0ff4df2d988ad1e0b3d2414bd50480f1ae8acc
tree766ea0b74a27945cf9a88eabcf6775774905a7d5
parent968bbc892e5e44c50fd2d55c975f785401ef2bcf
[libbacktrace] Don't point to released memory in backtrace_vector_release

When backtrace_vector_release is called with vec.size == 0, it releases the
memory pointed at by vec.base.

Set vec.base set to NULL if vec.size == 0 to ensure we don't point to released
memory.

Bootstrapped and reg-tested on x86_64.

2018-11-27  Tom de Vries  <tdevries@suse.de>

* mmap.c (backtrace_vector_release): Same.
* unittest.c (test1): Add check.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@266505 138bc75d-0d04-0410-961f-82ee72b054a4
libbacktrace/ChangeLog
libbacktrace/mmap.c
libbacktrace/unittest.c