From: Simon Marchi <simark@simark.ca>
To: Simon Marchi <simon.marchi@efficios.com>,
"Gerlicher, Klaus" <klaus.gerlicher@intel.com>,
Andrew Burgess <aburgess@redhat.com>
Cc: "Simon.Marchi@amd.com" <Simon.Marchi@amd.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: reject inserting breakpoints between functions
Date: Thu, 29 Aug 2024 15:01:32 -0400 [thread overview]
Message-ID: <61b747ca-adfe-4d06-b36e-5b4d38a769e2@simark.ca> (raw)
In-Reply-To: <cd740760-2fa3-4355-b26d-69bbb95cc3e0@efficios.com>
On 2024-08-12 10:54, Simon Marchi wrote:
> On 8/7/24 4:27 AM, Gerlicher, Klaus wrote:
>> Hi Simon,
>>
>> Kindly reminding again about your breakpoint sliding patch.
>>
>> I worked a bit with it, I have had one additional issue that would be fixed with below patch but of course since your original patch hasn't landed yet I can't post this as a real patch.
>>
>> So if you want to integrate this to your patch or treat this in another way, please let me know.
>>
>> Thanks
>> Klaus
>
> Thanks for reminding me... I'll try to come back to this this week.
>
> Simon
I went ahead and pushed Andrew's version of my patch, with one
small change, to use a reference instead of a pointer.
Klaus, can you rebase and re-post your patch?
Simon
next prev parent reply other threads:[~2024-08-29 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 20:05 Simon Marchi via Gdb-patches
2022-06-17 16:25 ` Lancelot SIX via Gdb-patches
2022-06-21 17:01 ` Andrew Burgess via Gdb-patches
2024-04-30 8:47 ` Klaus Gerlicher
[not found] ` <6630b03f.050a0220.6a68d.6289SMTPIN_ADDED_BROKEN@mx.google.com>
2024-05-01 9:47 ` Andrew Burgess
2024-05-01 18:11 ` Simon Marchi
2024-05-08 14:26 ` Andrew Burgess
2024-08-07 8:27 ` Gerlicher, Klaus
2024-08-12 14:54 ` Simon Marchi
2024-08-29 19:01 ` Simon Marchi [this message]
2024-08-30 5:38 ` Gerlicher, Klaus
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=61b747ca-adfe-4d06-b36e-5b4d38a769e2@simark.ca \
--to=simark@simark.ca \
--cc=Simon.Marchi@amd.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=klaus.gerlicher@intel.com \
--cc=simon.marchi@efficios.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