From: Simon Marchi <simark@simark.ca>
To: 紀重禕 <demonic@csie.io>, gdb-patches@sourceware.org
Subject: Re: [PATCH] breakpoint.c: Fix advance/until and multiple locations
Date: Wed, 26 Aug 2020 22:03:34 -0400 [thread overview]
Message-ID: <27c4a444-3b72-3b00-ec23-5e6e9082d5e7@simark.ca> (raw)
In-Reply-To: <CA+YVB3TT=nrUthDkzPE66Bc0_FySVNEvTQ9P+sfT-FrqD_yeew@mail.gmail.com>
On 2020-08-26 11:06 a.m., 紀重禕 wrote:
> Fix bug 26524 <https://sourceware.org/bugzilla/show_bug.cgi?id=26524> ,
> iterate the sals variable to insert a breakpoint for each <location>
>
> --
> Best regards,
> Chung-Yi Chi
>
Hi,
I'm not sure the approach is right, since you end up creating multiple until_break_fsm
objects (one for each sal) and overwriting them.
Pedro Alves posted some patches fixing the same problem here:
https://sourceware.org/pipermail/gdb-patches/2020-August/171427.html
which look good to me. Could you please take a look at those?
Simon
next prev parent reply other threads:[~2020-08-27 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 15:06 紀重禕
2020-08-27 2:03 ` Simon Marchi [this message]
2020-08-27 2:17 ` 紀重禕
2020-08-27 2:22 ` Simon Marchi
2020-08-27 20:27 ` Pedro Alves
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=27c4a444-3b72-3b00-ec23-5e6e9082d5e7@simark.ca \
--to=simark@simark.ca \
--cc=demonic@csie.io \
--cc=gdb-patches@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