libc.so.6 dependencies

[Alex Ernst]

Hi Florian,

Yes, you are right.

Thx,
Alex


On Wed, Jun 25, 2025 at 9:23 AM Florian Weimer <fweimer@redhat.com> wrote:

> * Alex Ernst:
>
> > Hello Adhemerval and Florian,
> >
> > Thank you very much for these clarifications. Very sad to hear all of
> this.
> >
> > Probably, a workaround would be to define app's own pthread_cancel()
> function:
> >
> > #include <pthread.h>
> > #include <signal.h>
> > int pthread_cancel(pthread_t thread)
> > {
> >    return pthread_kill(thread,SIGTERM);
> > }
>
> That's not the same as the historic behavior.  In a single-threaded
> application, you would just call exit(0) to achieve that.
>
> > I do not know, it might have some side effects. And it looks like (in
> > sake of consistency) glibc should process pthread_kill() similarly to
> > pthread_cancel() :)
> >
> > libgcc_s.so.1 must be installed for unwinding to work
> > libgcc_s.so.1 must be installed for pthread_cancel to work
> > libgcc_s.so.1 must be installed for pthread_kill to work !!!
> > libgcc_s.so.1 must be installed for pthread_exit to work
>
> Why would we need libgcc_s.so.1 for pthread_kill?  What it does depends
> on the signal handler the application has registered, but glibc on its
> own does not perform any unwindg.
>
> Thanks,
> Florian
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20250625/03064ff9/attachment.htm>