From 352ed7b4c28a32bfad7f189dd4c8bd0ec5f4fca2 Mon Sep 17 00:00:00 2001 From: Michael Snyder Date: Fri, 11 Jan 2002 01:46:17 +0000 Subject: 2002-01-10 Michael Snyder * NEWS: Mention --pid and corefile/proc-id behavior change. --- gdb/ChangeLog | 2 ++ gdb/NEWS | 17 +++++++++++++++++ 2 files changed, 19 insertions(+) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index f26b715..6647f4d 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -5,6 +5,8 @@ 2002-01-10 Michael Snyder + * NEWS: Mention --pid and corefile/proc-id behavior change. + * Makefile.in: Add rules for gcore.o and linux-proc.o. * gcore.c: Include cli/cli-decode.h instead of command.h. diff --git a/gdb/NEWS b/gdb/NEWS index d597611..39b33fe 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -3,6 +3,23 @@ *** Changes since GDB 5.1: +* New command line option + +GDB now accepts --pid or -p followed by a process id. + +* Change in command line behavior -- corefiles vs. process ids. + +There is a subtle behavior in the way in which GDB handles +command line arguments. The first non-flag argument is always +a program to debug, but the second non-flag argument may either +be a corefile or a process id. Previously, GDB would attempt to +open the second argument as a corefile, and if that failed, would +issue a superfluous error message and then attempt to attach it as +a process. Now, if the second argument begins with a non-digit, +it will be treated as a corefile. If it begins with a digit, +GDB will attempt to attach it as a process, and if no such process +is found, will then attempt to open it as a corefile. + * New native configurations x86 OpenBSD i[3456]86-*-openbsd* -- cgit v1.1