public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/28796] GDB locks up after stopping on a breakpoint in invalidated memory on aarch64
Date: Thu, 10 Nov 2022 00:45:46 +0000	[thread overview]
Message-ID: <bug-28796-4717-oJrTRbALci@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28796-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28796

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Luis Machado <luisgpm@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=94355de7751579b0182bd5821a3223939054f5d7

commit 94355de7751579b0182bd5821a3223939054f5d7
Author: Luis Machado <luis.machado@arm.com>
Date:   Mon Oct 31 13:26:20 2022 +0000

    [gdb/aarch64] Use safer memory read routines

      PR tdep/28796

      As reported, we are using some memory read routines that don't handle
read
      errors gracefully. Convert those to use the safe_* versions if available.

      This allows the code to handle those read errors in a more sensible way.

      Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28796

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-11-10  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20  9:41 [Bug tdep/28796] New: " idan.horowitz at gmail dot com
2022-01-20  9:44 ` [Bug tdep/28796] " idan.horowitz at gmail dot com
2022-10-21 10:11 ` luis.machado at arm dot com
2022-10-21 10:11 ` luis.machado at arm dot com
2022-11-10  0:45 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-10  0:46 ` luis.machado at arm dot com

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=bug-28796-4717-oJrTRbALci@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).