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 gdb/27338] Stepping over a breakpoint on an instruction that makes the thread exit is not correctly handled Date: Mon, 13 Nov 2023 14:26:35 +0000 [thread overview] Message-ID: <bug-27338-4717-9WDjcKr2uH@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27338-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27338 --- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Pedro Alves <palves@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a51e14efe29d64a966161837e991193efb2e2457 commit a51e14efe29d64a966161837e991193efb2e2457 Author: Pedro Alves <pedro@palves.net> Date: Mon Mar 21 19:09:13 2022 +0000 Implement GDB_THREAD_OPTION_EXIT support for native Linux This implements support for the new GDB_THREAD_OPTION_EXIT thread option for native Linux. Reviewed-By: Andrew Burgess <aburgess@redhat.com> Change-Id: Ia69fc0b9b96f9af7de7cefc1ddb1fba9bbb0bb90 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27338 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-13 14:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-03 20:00 [Bug gdb/27338] New: " simark at simark dot ca 2021-02-03 20:00 ` [Bug gdb/27338] " simark at simark dot ca 2021-02-03 21:37 ` simark at simark dot ca 2022-06-21 11:24 ` pedro at palves dot net 2023-03-27 16:20 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:26 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:26 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:26 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-13 14:26 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:27 ` cvs-commit at gcc dot gnu.org 2023-11-13 15:03 ` pedro at palves dot net
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-27338-4717-9WDjcKr2uH@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: linkBe 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).