"Also sprach Debian Bug Tracking System:"
> >signal 11 received in pid 21020 after 1 cancel signals
> >Segmentation fault
> >
> > The thread is just sitting in a nanosleep, as I said.
> >
> > It makes no difference if a handler for SEGV is set or not - it just
> > prints the output messag
Package: libc6-dev
Version: 2.7-4
Severity: normal
The following program exits with SEGV after sending a cancel signal to a
single thread which is sitting in a nanosleep for 10s, with no mutexes held
anywhere. The thread gets the segv, as far as I can tell in the handler,
not the parent.
The pro
2 matches
Mail list logo