From: Florian Weimer <firstname.lastname@example.org>
To: Mathieu Desnoyers <email@example.com>
Cc: libc-alpha <firstname.lastname@example.org>,
Simon Marchi <email@example.com>,
Subject: Re: rseq and gdb
Date: Thu, 16 Dec 2021 22:12:54 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <1507387605.36435.1639688959308.JavaMail.email@example.com> (Mathieu Desnoyers's message of "Thu, 16 Dec 2021 16:09:19 -0500 (EST)")
* Mathieu Desnoyers:
> I suspect that gdb should ideally do something to allow it to
> single-step through rseq critical sections. In librseq , we emit
> the __rseq_cs_ptr_array and __rseq_exit_point_array sections to allow
> gdb to know about rseq critical sections and skip over those critical
> sections as needed. Otherwise single-stepping over each instruction of
> a rseq critical section will loop forever.
That's probably something that should be expressed in the DWARF data.
> Now that glibc plans to enable rseq by default starting with glibc 2.35,
> it appears to be a good timing to raise this topic with the gdb community.
It's less of an issue than the CRIU problem that we discussed because it
will only affect attempts to debug actually rseq-using applications.
(The CRIU problem affects everything.) Not saying that debugging
support isn't important, just trying to put it into perspective. 8-)
next prev parent reply other threads:[~2021-12-16 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 21:09 Mathieu Desnoyers
2021-12-16 21:12 ` Florian Weimer [this message]
2021-12-17 15:51 ` Simon Marchi
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).