glibc problem.

Jakub Jelinek jakub at redhat.com
Fri Sep 24 15:28:31 UTC 2004


On Fri, Sep 24, 2004 at 11:04:31AM -0400, Robert Couture wrote:
> sigemptyset()
> sigaddset()
> pthread_sigmask()
> sigwait()
> 
> When I reverted back to glibc-2.3.3-54 (common, header, devel) the
> problem went away.

The most important change between -54 and -55 was the set{res,re,e}[ug]id
fix.
These functions must affect the whole process, while previously they
impacted on the current thread only.

Can you see if your app is 1) threaded 2) calls one of these functions?
(you can see it e.g. in LD_DEBUG=all dump).

Another change (related) was that in NPTL SIGRTMIN increased, so if
the application hardcodes signal 33 for something instead of using SIGRTMIN,
the problem might be there.

	Jakub





More information about the fedora-test-list mailing list