From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] Remove ALL_BREAKPOINTS_SAFE
Date: Mon, 8 May 2023 10:59:38 -0400 [thread overview]
Message-ID: <42f0ef87-b803-e614-176a-7c576117fbf2@simark.ca> (raw)
In-Reply-To: <7936dc5e-12ca-bf6e-dbfa-54f6f690801e@simark.ca>
On 5/7/23 22:24, Simon Marchi via Gdb-patches wrote:
> On 4/16/23 12:28, Tom Tromey wrote:
>> There's just a single remaining use of the ALL_BREAKPOINTS_SAFE macro;
>> this patch replaces it with a for-each and an explicit temporary
>> variable.
>
> Starting with this patch, I see:
>
> (gdb) PASS: gdb.base/stale-infcall.exp: continue to breakpoint: break-run1
> print infcall ()
> =================================================================
> ==47472==ERROR: AddressSanitizer: heap-use-after-free on address 0x611000034980 at pc 0x563f7012c7bc bp 0x7ffdf3804d70 sp 0x7ffdf3804d60
> READ of size 8 at 0x611000034980 thread T0
I just sent a patch for this:
https://inbox.sourceware.org/gdb-patches/20230508145913.29359-1-simon.marchi@efficios.com/T/#u
Simon
prev parent reply other threads:[~2023-05-08 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 16:28 [PATCH 0/4] Remove remaining ALL_ iterator macros Tom Tromey
2023-04-16 16:28 ` [PATCH 1/4] Rename objfile::sections Tom Tromey
2023-04-17 17:57 ` Keith Seitz
2023-05-07 18:43 ` Tom Tromey
2023-04-16 16:28 ` [PATCH 2/4] Remove ALL_OBJFILE_OSECTIONS Tom Tromey
2023-04-16 16:28 ` [PATCH 3/4] Remove ALL_DICT_SYMBOLS Tom Tromey
2023-04-16 16:28 ` [PATCH 4/4] Remove ALL_BREAKPOINTS_SAFE Tom Tromey
2023-05-08 2:24 ` Simon Marchi
2023-05-08 14:59 ` Simon Marchi [this message]
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=42f0ef87-b803-e614-176a-7c576117fbf2@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).