mirror of
https://github.com/darlinghq/darling-gdb.git
synced 2025-02-03 15:42:52 +00:00
2002-01-10 Michael Snyder <msnyder@redhat.com>
* NEWS: Mention --pid and corefile/proc-id behavior change.
This commit is contained in:
parent
ae940673aa
commit
352ed7b4c2
@ -5,6 +5,8 @@
|
||||
|
||||
2002-01-10 Michael Snyder <msnyder@redhat.com>
|
||||
|
||||
* 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.
|
||||
|
||||
|
17
gdb/NEWS
17
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*
|
||||
|
Loading…
x
Reference in New Issue
Block a user