Remove gcore's -s option.

It has no effect and is always implicitly set since ptrace(2) stops the
target process.

usr.bin/gcore/extern.h

@@ -31,7 +31,6 @@
  */
 
 #define	PFLAGS_FULL	0x01
-#define	PFLAGS_RESUME	0x02
 
 struct dumpers {
 	int (*ident)(int efd, pid_t pid, char *binfile);

usr.bin/gcore/gcore.1

@@ -28,7 +28,7 @@
 .\"	@(#)gcore.1	8.2 (Berkeley) 4/18/94
 .\" $FreeBSD$
 .\"
-.Dd July 14, 2010
+.Dd July 13, 2016
 .Dt GCORE 1
 .Os
 .Sh NAME
@@ -37,7 +37,6 @@
 .Sh SYNOPSIS
 .Nm
 .Op Fl f
-.Op Fl s
 .Op Fl c Ar core
 .Op Ar executable
 .Ar pid
@@ -66,15 +65,6 @@ behavior.
 As a result, this flag should only be used when the behavior of the
 application and any devices it has mapped is fully understood and any side
 effects can be controlled or tolerated.
-.It Fl s
-Stop the process while gathering the core image, and resume it
-when done.
-This guarantees that the resulting core dump will
-be in a consistent state.
-The process is resumed even if it was
-already stopped.
-The same effect can be achieved manually with
-.Xr kill 1 .
 .El
 .Sh FILES
 .Bl -tag -width /var/log/messages -compact

usr.bin/gcore/gcore.c

@@ -87,7 +87,7 @@ main(int argc, char *argv[])
 
 	pflags = 0;
 	corefile = NULL;
-        while ((ch = getopt(argc, argv, "c:fs")) != -1) {
+        while ((ch = getopt(argc, argv, "c:f")) != -1) {
                 switch (ch) {
                 case 'c':
 			corefile = optarg;
@@ -95,9 +95,6 @@ main(int argc, char *argv[])
 		case 'f':
 			pflags |= PFLAGS_FULL;
 			break;
-		case 's':
-			pflags |= PFLAGS_RESUME;
-			break;
 		default:
 			usage();
 			break;