Print this page
Code review comments from jeffpc
   1 '\" te
   2 .\" Copyright (C) 2008, Sun Microsystems, Inc. All Rights Reserved.
   3 .\" Copyright 2012 DEY Storage Systems, Inc.  All rights reserved.
   4 .\" Copyright (c) 2013, Joyent, Inc. All rights reserved.
   5 .\" Copyright 1989 AT&T
   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 .\" 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 .\" 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 "Jul 23, 2015"
  10 .SH NAME
  11 core \- process core file
  12 .SH DESCRIPTION
  13 .LP
  14 The operating system writes out a core file for a process when the process is
  15 terminated due to receiving certain signals. A core file is a disk copy of the
  16 contents of the process address space at the time the process received the
  17 signal, along with additional information about the state of the process. This
  18 information can be consumed by a debugger. Core files can also be generated by
  19 applying the \fBgcore\fR(1) utility to a running process.
  20 .sp
  21 .LP
  22 Typically, core files are produced following abnormal termination of a process
  23 resulting from a bug in the corresponding application. Whatever the cause, the
  24 core file itself provides invaluable information to the programmer or support
  25 engineer to aid in diagnosing the problem. The core file can be inspected using
  26 a debugger such as \fBdbx\fR(1) or \fBmdb\fR(1) or by applying one of the
  27 \fBproc\fR(1) tools.
  28 .sp
  29 .LP


   1 '\" te
   2 .\" Copyright (C) 2008, Sun Microsystems, Inc. All Rights Reserved.
   3 .\" Copyright 2012 DEY Storage Systems, Inc.  All rights reserved.
   4 .\" Copyright (c) 2013, Joyent, Inc. All rights reserved.
   5 .\" Copyright 1989 AT&T
   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 .\" 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 .\" 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 "Jun 6, 2016"
  10 .SH NAME
  11 core \- process core file
  12 .SH DESCRIPTION
  13 .LP
  14 The operating system writes out a core file for a process when the process is
  15 terminated due to receiving certain signals. A core file is a disk copy of the
  16 contents of the process address space at the time the process received the
  17 signal, along with additional information about the state of the process. This
  18 information can be consumed by a debugger. Core files can also be generated by
  19 applying the \fBgcore\fR(1) utility to a running process.
  20 .sp
  21 .LP
  22 Typically, core files are produced following abnormal termination of a process
  23 resulting from a bug in the corresponding application. Whatever the cause, the
  24 core file itself provides invaluable information to the programmer or support
  25 engineer to aid in diagnosing the problem. The core file can be inspected using
  26 a debugger such as \fBdbx\fR(1) or \fBmdb\fR(1) or by applying one of the
  27 \fBproc\fR(1) tools.
  28 .sp
  29 .LP