diff options
| author | Michael Snyder <msnyder@vmware.com> | 2002-01-11 01:46:17 +0000 |
|---|---|---|
| committer | Michael Snyder <msnyder@vmware.com> | 2002-01-11 01:46:17 +0000 |
| commit | 352ed7b4c28a32bfad7f189dd4c8bd0ec5f4fca2 (patch) | |
| tree | 1ca382a12e45e1d30be0e5d3fa00d74ff99c6795 /gdb/NEWS | |
| parent | ae940673aaad281db6a05a87d4bc5d4d60d4f3ab (diff) | |
| download | gdb-352ed7b4c28a32bfad7f189dd4c8bd0ec5f4fca2.zip gdb-352ed7b4c28a32bfad7f189dd4c8bd0ec5f4fca2.tar.gz gdb-352ed7b4c28a32bfad7f189dd4c8bd0ec5f4fca2.tar.bz2 | |
2002-01-10 Michael Snyder <msnyder@redhat.com>
* NEWS: Mention --pid and corefile/proc-id behavior change.
Diffstat (limited to 'gdb/NEWS')
| -rw-r--r-- | gdb/NEWS | 17 |
1 files changed, 17 insertions, 0 deletions
@@ -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* |