This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/15521] New: real-time signals DO NOT delivered starting with the lowest-numbered signal.
- From: "1533963612 at qq dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 23 May 2013 08:19:49 +0000
- Subject: [Bug libc/15521] New: real-time signals DO NOT delivered starting with the lowest-numbered signal.
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15521
Bug #: 15521
Summary: real-time signals DO NOT delivered starting with the
lowest-numbered signal.
Product: glibc
Version: 2.15
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: unassigned@sourceware.org
ReportedBy: 1533963612@qq.com
CC: drepper.fsp@gmail.com
Classification: Unclassified
Created attachment 7040
--> http://sourceware.org/bugzilla/attachment.cgi?id=7040
compile it using -std=c99 option
Assume parent send 3 signals from SIGRTMAX to SIGRTMAX - 2, each signal sends 3
times, the child would recv the signal as order SIGRTMAX - 2 to SIGRTMAX, since
the lowest-numbered should delivered first, and each same number signal deliver
as FIFO order, but the result is:
-----parent send-----
sent 64, val = 1
sent 64, val = 2
sent 64, val = 3
sent 63, val = 1
sent 63, val = 2
sent 63, val = 3
sent 62, val = 1
sent 62, val = 2
sent 62, val = 3
-----child recv-----
recv 64, val = 1
recv 64, val = 2
recv 64, val = 3
recv 63, val = 1
recv 63, val = 2
recv 63, val = 3
recv 62, val = 1
recv 62, val = 2
recv 62, val = 3
we see that the same number signal deliver in rigth sequence ïFIFOïï but
different signal DO NOT delivered in lowest number first, in this case, should
signal 62 first, and 64 last.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.