This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. a41f2563d040d86954ccda7faa4a8ad7bdbcae88
- From: gingold at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 1 Apr 2014 09:51:35 -0000
- Subject: gdb and binutils branch master updated. a41f2563d040d86954ccda7faa4a8ad7bdbcae88
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 a41f2563d040d86954ccda7faa4a8ad7bdbcae88 (commit)
from 98d1b8dcd84bb39ba5d0731162f241890d4ce5f5 (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=a41f2563d040d86954ccda7faa4a8ad7bdbcae88
commit a41f2563d040d86954ccda7faa4a8ad7bdbcae88
Author: Tristan Gingold <tristan.gingold@adacore.com>
Date: Fri Mar 21 16:56:39 2014 +0100
darwin-nat: avoid crash while debugging gdb.
it is possible that gdb gets mach exceptions from an unknown inferior. This
happens when an inferior creates a child and that child gets a signal.
So instead of reporting messages with unknown origins, simply reply to these
notifications. The kernel will then post the unix signal.
gdb/
* darwin-nat.c (darwin_encode_reply): Add prototype.
(darwin_decode_exception_message): Reply to unknown inferiors.
(darwin_decode_message): Handle message by id. Ignore message
to unknown inferior.
(darwin_wait): Discard unknown messages, add debug trace.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 8 +++
gdb/darwin-nat.c | 144 +++++++++++++++++++++++++++++++++--------------------
2 files changed, 98 insertions(+), 54 deletions(-)
hooks/post-receive
--
gdb and binutils