public inbox for
help / color / mirror / Atom feed
Subject: gdb and binutils branch master updated. 1ed6c797ef8814d7f273a0ccc5cf7ebbce497933
Date: Thu, 07 Nov 2013 16:03:00 -0000	[thread overview]
Message-ID: <> (raw)

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  1ed6c797ef8814d7f273a0ccc5cf7ebbce497933 (commit)
       via  8782aa321e1bb466012a71791b8a40e2cb42d841 (commit)
      from  a22bc58c6ad25f1a2af7c93f3beeb4f927535329 (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 -----------------------------------------------------------------;h=1ed6c797ef8814d7f273a0ccc5cf7ebbce497933

commit 1ed6c797ef8814d7f273a0ccc5cf7ebbce497933
Author: Will Newton <>
Date:   Tue Oct 29 09:43:07 2013 -0700

    sim/arm: Prevent crash when running sim with no binary.
    2013-11-07  Will Newton  <>
    	PR gdb/15508
    	* arm/wrapper.c (sim_create_inferior): Call init before
    	accessing STATE.;h=8782aa321e1bb466012a71791b8a40e2cb42d841

commit 8782aa321e1bb466012a71791b8a40e2cb42d841
Author: Will Newton <>
Date:   Tue Oct 29 09:20:48 2013 -0700

    sim/arm: Prevent NULL pointer dereference in sim_create_inferior.
    2013-11-07  Will Newton  <>
    	PR gdb/9195
    	* arm/wrapper.c (sim_create_inferior): Avoid calling
    	bfd_get_mach with a NULL bfd.


Summary of changes:
 sim/ChangeLog     |   12 ++++++++++++
 sim/arm/wrapper.c |   14 ++++++++++----
 2 files changed, 22 insertions(+), 4 deletions(-)

gdb and binutils

                 reply	other threads:[~2013-11-07 16:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).