public inbox for
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <>
To: Florian Weimer <>
Cc: libc-alpha <>,
	 Simon Marchi <>,
Subject: rseq and gdb
Date: Thu, 16 Dec 2021 16:09:19 -0500 (EST)	[thread overview]
Message-ID: <> (raw)

Hi Florian,

I suspect that gdb should ideally do something to allow it to single-step
through rseq critical sections. In librseq [1], 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

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.




Mathieu Desnoyers
EfficiOS Inc.

             reply	other threads:[~2021-12-16 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 21:09 Mathieu Desnoyers [this message]
2021-12-16 21:12 ` Florian Weimer
2021-12-17 15:51   ` Simon Marchi

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:

* 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).