Print this page
Code review comments from jeffpc
7029 want per-process exploit mitigation features (secflags)
7030 want basic address space layout randomization (aslr)
7031 noexec_user_stack should be a secflag
7032 want a means to forbid mappings around NULL.

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man4/core.4
          +++ new/usr/src/man/man4/core.4
   1    1  '\" te
   2    2  .\" Copyright (C) 2008, Sun Microsystems, Inc. All Rights Reserved.
   3    3  .\" Copyright 2012 DEY Storage Systems, Inc.  All rights reserved.
   4    4  .\" Copyright (c) 2013, Joyent, Inc. All rights reserved.
   5    5  .\" Copyright 1989 AT&T
   6    6  .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   7    7  .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   8    8  .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   9      -.TH CORE 4 "Mar 31, 2013"
        9 +.TH CORE 4 "Jun 6, 2016"
  10   10  .SH NAME
  11   11  core \- process core file
  12   12  .SH DESCRIPTION
  13      -.sp
  14   13  .LP
  15   14  The operating system writes out a core file for a process when the process is
  16   15  terminated due to receiving certain signals. A core file is a disk copy of the
  17   16  contents of the process address space at the time the process received the
  18   17  signal, along with additional information about the state of the process. This
  19   18  information can be consumed by a debugger. Core files can also be generated by
  20   19  applying the \fBgcore\fR(1) utility to a running process.
  21   20  .sp
  22   21  .LP
  23   22  Typically, core files are produced following abnormal termination of a process
↓ open down ↓ 420 lines elided ↑ open up ↑
 444  443  \fB\fBpsinfo_t\fR\fR
 445  444  .ad
 446  445  .RS 15n
 447  446  \fBn_type\fR: \fBNT_SPYMASTER\fR. This entry is present only for an agent
 448  447  LWP and contains the \fBpsinfo_t\fR of the process that created the agent
 449  448  LWP. See the \fBproc\fR(4) description of the \fBspymaster\fR entry for
 450  449  more details.
 451  450  .RE
 452  451  
 453  452  .sp
      453 +.ne 2
      454 +.na
      455 +\fB\fBprsecflags_t\fR\fR
      456 +.ad
      457 +.RS 15n
      458 +\fBn_type\fR: \fbNT_SECFLAGS\fR.  This entry contains the process
      459 +security-flags, see \fBsecurity-flags\fR(5), \fBproc\fR(4), and
      460 +\fBpsecflags\fR(1M) for more information.
      461 +.RE
      462 +
      463 +.sp
 454  464  .LP
 455  465  Depending on the \fBcoreadm\fR(1M) settings, the section header of an ELF core
 456  466  file can contain entries for CTF, symbol table, and string table sections. The
 457  467  \fBsh_addr\fR fields are set to the base address of the first mapping of the
 458  468  load object that they came from to. This can be used to match those sections
 459  469  with the corresponding load object.
 460  470  .sp
 461  471  .LP
 462  472  The size of the core file created by a process can be controlled by the user
 463  473  (see \fBgetrlimit\fR(2)).
 464  474  .SH SEE ALSO
 465      -.sp
 466  475  .LP
 467  476  \fBelfdump\fR(1), \fBgcore\fR(1), \fBmdb\fR(1), \fBproc\fR(1), \fBps\fR(1),
 468  477  \fBcoreadm\fR(1M), \fBgetrlimit\fR(2), \fBsetrlimit\fR(2), \fBsetuid\fR(2),
 469  478  \fBsysinfo\fR(2), \fBuname\fR(2), \fBgetzonenamebyid\fR(3C),
 470  479  \fBgetzoneid\fR(3C), \fBelf\fR(3ELF), \fBsignal.h\fR(3HEAD), \fBa.out\fR(4),
 471      -\fBproc\fR(4), \fBzones\fR(5)
      480 +\fBproc\fR(4), \fBzones\fR(5), \fBsecurity-flags\fR(5)
 472  481  .sp
 473  482  .LP
 474  483  \fIANSI C Programmer's Guide\fR
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX