Page Menu
Home
FreeBSD
Search
Configure Global Search
Log In
Files
F142328347
D7118.diff
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Flag For Later
Award Token
Size
1 KB
Referenced Files
None
Subscribers
None
D7118.diff
View Options
Index: head/share/man/man3/siginfo.3
===================================================================
--- head/share/man/man3/siginfo.3
+++ head/share/man/man3/siginfo.3
@@ -27,7 +27,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd September 14, 2012
+.Dd July 14, 2016
.Dt SIGINFO 3
.Os
.Sh NAME
@@ -54,7 +54,7 @@
.Vt siginfo_t ,
which includes the following information:
.Bl -column ".Vt union signal" ".Va si_overrun"
-.It Sy "Type Member Description"
+.It Sy Type Ta Sy Member Ta Sy Description
.It Vt int Ta Va si_signo Ta
signal number
.It Vt int Ta Va si_errno Ta
@@ -107,7 +107,7 @@
that are signal-specific or non-signal-specific reasons why the signal was
generated:
.Bl -column ".Dv SIGPOLL" ".Dv CLD_CONTINUED"
-.It Sy "Signal Code Reason"
+.It Sy Signal Ta Sy Code Ta Sy Reason
.It Dv SIGILL Ta Dv ILL_ILLOPC Ta
illegal opcode
.It Ta Dv ILL_ILLOPN Ta
@@ -206,7 +206,7 @@
.Pp
In addition, the following signal-specific information is available:
.Bl -column ".Dv SIGPOLL" ".Dv CLD_CONTINUED"
-.It Sy "Signal Member Value"
+.It Sy Signal Ta Sy Member Ta Sy Value
.It Dv SIGILL Ta Va si_addr Ta
address of faulting instruction
.It Ta Va si_trapno Ta
@@ -240,8 +240,8 @@
.El
.Pp
Finally, the following code-specific information is available:
-.Bl -column ".Dv SI_QUEUE" ".Va si_overrun"
-.It Sy "Code Member Value"
+.Bl -column ".Dv SI_ASYNCIO" ".Va si_overrun"
+.It Sy Code Ta Sy Member Ta Sy Value
.It Dv SI_USER Ta Va si_pid Ta
the process ID that sent the signal
.It Ta Va si_uid Ta
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Mon, Jan 19, 3:34 PM (7 h, 2 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
27748513
Default Alt Text
D7118.diff (1 KB)
Attached To
Mode
D7118: Fix rendering issues in siginfo(3).
Attached
Detach File
Event Timeline
Log In to Comment