diff options
| author | Andreas Arnez <arnez at linux dot vnet dot ibm dot com> | 2013-11-13 14:00:44 +0100 |
|---|---|---|
| committer | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2013-11-15 17:25:23 +0100 |
| commit | 19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f (patch) | |
| tree | bfc1154d1345b7094bf073a2895d4941d2acdcfe /lt~obsolete.m4 | |
| parent | e092da29031a5a5a74beb1d671da98d55fff6ebd (diff) | |
| download | gdb-19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f.zip gdb-19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f.tar.gz gdb-19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f.tar.bz2 | |
Fix GDB crash with upstream GCC due to memcpy(NULL, ...)
Similar to qsort(), the glibc version of memcpy() also declares its
arguments with __attribute__(__nonnull__(...)). If NULL is passed
anyway, upstream GCC's new pass '-fisolate-erroneous-paths' typically
causes a trap in such cases. I've encountered this with GDB in
chain_candidate() when trying to execute the break.exp test case.
gdb/
2013-11-13 Andreas Arnez <arnez@linux.vnet.ibm.com>
* dwarf2loc.c (chain_candidate): Prevent invoking memcpy with
NULL.
Diffstat (limited to 'lt~obsolete.m4')
0 files changed, 0 insertions, 0 deletions