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 ada/25811] [ada] start attempts to set breakpoint on main of previous exec Date: Tue, 05 Sep 2023 16:05:42 +0000 [thread overview] Message-ID: <bug-25811-4717-AnC9BuZsf7@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25811-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25811 --- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=358be6e72d464349e5146095bdb04b96be5734c1 commit 358be6e72d464349e5146095bdb04b96be5734c1 Author: Tom Tromey <tromey@adacore.com> Date: Mon Aug 21 09:55:14 2023 -0600 Read Ada main name from executable, not inferior An upstream bug report points out this bug: if the user switches from one Ada executable to another without "kill"ing the inferior, then the "start" command will fail. What happens here is that the Ada "main" name is found in a constant string in the executable. But, if the inferior is running, then the process_stratum target reads from the inferior memory. This patch fixes the problem by changing the main name code to set trust-readonly-sections, causing the target stack to read from the executable instead. I looked briefly at changing GNAT to emit DW_AT_main_subprogram instead, but this looks to be pretty involved. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=25811 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-05 16:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-10 16:33 [Bug ada/25811] New: " vries at gcc dot gnu.org 2023-04-19 18:40 ` [Bug ada/25811] " tromey at sourceware dot org 2023-08-21 15:41 ` tromey at sourceware dot org 2023-08-23 17:12 ` tromey at sourceware dot org 2023-09-05 16:05 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-05 16:06 ` tromey at sourceware dot org
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-25811-4717-AnC9BuZsf7@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).