Re: --pid and --core

[Pedro Alves <pedro_alves@portugalmail.pt>]

[-- Attachment #1: Type: text/plain, Size: 409 bytes --]

Eli Zaretskii wrote:
>> Thanks, but please make the appropriate changes in the manual as
>> well.  It currently says:
>>
>>     `-pid NUMBER'
>>     `-p NUMBER'
>> 	 Connect to process ID NUMBER, as with the `attach' command.  If
>> 	 there is no such process, GDB will attempt to open a core file
>> 	 named NUMBER.
> 
> In addition, this change also warrants a NEWS entry.
> 

Like so ?

-- 
Pedro Alves




[-- Attachment #2: pid_core_doc.diff --]
[-- Type: text/x-diff, Size: 1789 bytes --]

2008-01-05  Pedro Alves  <pedro@codesourcery.com>

	gdb/

	* NEWS: Mention --pid and --core command line behaviour changes.

2008-01-05  Pedro Alves  <pedro@codesourcery.com>

	gdb/doc/

	* gdb.texinfo (File Options): Remove mention of the attempt to
	open a core file with the -p option.  Don't list -c as a valid
	option to attach to a process.

---
 gdb/NEWS            |    7 +++++++
 gdb/doc/gdb.texinfo |    3 ---
 2 files changed, 7 insertions(+), 3 deletions(-)

Index: src/gdb/NEWS
===================================================================
--- src.orig/gdb/NEWS	2008-01-05 17:22:19.000000000 +0000
+++ src/gdb/NEWS	2008-01-05 17:24:16.000000000 +0000
@@ -3,6 +3,13 @@
 
 *** Changes since GDB 6.7
 
+* Change in command line behavior -- corefiles vs. process ids.
+
+  When the '-p NUMBER' or '--pid NUMBER' options are used, and
+  attaching to process NUMBER fails, GDB no longer attempts to open a
+  core file named NUMBER.  Attaching to a program using the -c option
+  is no longer supported.  Instead, use the '-p' or '--pid' options.
+
 * New commands
 
 set print frame-arguments (all|scalars|none)
Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo	2008-01-05 17:22:19.000000000 +0000
+++ src/gdb/doc/gdb.texinfo	2008-01-05 17:23:56.000000000 +0000
@@ -942,14 +942,11 @@ file.
 @cindex @code{-c}
 Use file @var{file} as a core dump to examine.
 
-@item -c @var{number}
 @item -pid @var{number}
 @itemx -p @var{number}
 @cindex @code{--pid}
 @cindex @code{-p}
 Connect to process ID @var{number}, as with the @code{attach} command.
-If there is no such process, @value{GDBN} will attempt to open a core
-file named @var{number}.
 
 @item -command @var{file}
 @itemx -x @var{file}