This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. 19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f
- From: uweigand at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 15 Nov 2013 16:25:55 -0000
- Subject: gdb and binutils branch master updated. 19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch, master has been updated
via 19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f (commit)
from e092da29031a5a5a74beb1d671da98d55fff6ebd (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f
commit 19a1b230f33dbcfa54cd1a9f88c2d5158f833f6f
Author: Andreas Arnez <arnez at linux dot vnet dot ibm dot com>
Date: Wed Nov 13 14:00:44 2013 +0100
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.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 5 +++++
gdb/dwarf2loc.c | 5 +++--
2 files changed, 8 insertions(+), 2 deletions(-)
hooks/post-receive
--
gdb and binutils