Draft e-mail: An async-signal-safe way to get thread’s stack

[Paul Pluzhnikov (Google Docs)]

Paul Pluzhnikov (ppluzhnikov@google.com) mentioned you in a comment in the  
following document
Draft e-mail: An async-signal-safe way to get thread’s stack  
(https://docs.google.com/document/d/1MaDQ_G4jf00yHygVFa-UjgXC1MVIHtD8dlm41vhvnE8/edit?resourcekey=0-hKu5iKZ_sOa-kZar2XsoqA&disco=AAACAhVdLBQ&usp=comment_email_document&ts=6a9ee019&usp_dm=false&tab=t.0)
This group may not have commenting rights to Draft e-mail: An  
async-signal-safe way to get thread’s stack.

1 comment

.
Paul Pluzhnikov
I am not sure whether CC'ing development lists, such as  
@libc-alpha@sourceware.org would be appropriate here.

I am not sure how many people are on libc-coord.

Open  
(https://docs.google.com/document/d/1MaDQ_G4jf00yHygVFa-UjgXC1MVIHtD8dlm41vhvnE8/edit?resourcekey=0-hKu5iKZ_sOa-kZar2XsoqA&disco=AAACAhVdLBQ&usp=comment_email_discussion&ts=6a9ee019&usp_dm=false)

Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA

You have received this email because you belong to a group mentioned in  
this thread. You cannot reply to this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20260907/cad14ab1/attachment.htm>