>Number:         10311
>Category:       bin
>Synopsis:       'gdb -k' should just work
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 07 14:19:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     John Hawkinson
>Release:        NetBSD 1.4.2
>Organization:
MIT
>Environment:
	
System: NetBSD zorkmid.mit.edu 1.4ZA NetBSD 1.4ZA (ZORKMID-$Revision: 1.13 $) #180: Wed Jun 7 16:31:23 EDT 2000 jhawk@zorkmid.mit.edu:/usr/local/current-src/sys/arch/i386/compile/ZORKMID i386


>Description:
	gdb -k netbsd.0 netbsd.0.core should "just work". It's really
silly to have to specify the kernel name with an interactive command
("target kcore").

	Really silly means:

	1.	A pain in the neck. More typing and less convenient.
		Also, the vaunted "gdb -k netbsd.11*" doesn't work.

	2.	Gratuitously different from precedent:

			a)	Userland.
			b)	other debuggers (e.g. adb -k)

	3.	Undocumented (this is covered by bin/8833).

If you think I'm wrong here, could someone please explain why
I'm wrong and why "target kcore" is better?

>How-To-Repeat:

zorkmid% gdb -k
-k: obsolete option.  For kernel debugging, start gdb
with just the kernel name as an argument (no core file)
and then use the gdb command `target kcore COREFILE'.
	
>Fix:
	Who's the NetBSD gdb maintainer? ;-)
>Release-Note:
>Audit-Trail:
>Unformatted: