This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20671] New: Conflicting descriptions of second command line argument (PID/core file) in Debugging with GDB
- From: "jarmo.jaakkola at roskakori dot fi" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 07 Oct 2016 11:32:53 +0000
- Subject: [Bug gdb/20671] New: Conflicting descriptions of second command line argument (PID/core file) in Debugging with GDB
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20671
Bug ID: 20671
Summary: Conflicting descriptions of second command line
argument (PID/core file) in Debugging with GDB
Product: gdb
Version: 7.12
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: jarmo.jaakkola at roskakori dot fi
Target Milestone: ---
The Debugging with GDB manual is unclear on how the second command line
argument (PID / core file) is handled because the information is provided in
two different places and the passages contain contradictory information.
According to section 2.1 a core file is tried first, but 2.1.1 says that
attaching to a process is tried first.
Section 2.1 Invoking GDB:
> You can, instead, specify a process ID as a second argument, if you
> want to debug a running process:
> gdb program 1234
> would attach gdb to process 1234 (unless you also have a file named
> 1234; gdb does check for a core file first).
2.1.1 Choosing Files:
> If the second argument begins with a decimal digit, gdb will first
> attempt to attach to it as a process, and if that fails, attempt
> to open it as a corefile.
--
You are receiving this mail because:
You are on the CC list for the bug.