ports/104271: devel/kdbg: fails to open core file

Andriy Gapon avg at icyb.net.ua
Tue Oct 10 16:10:45 UTC 2006


>Number:         104271
>Category:       ports
>Synopsis:       devel/kdbg: fails to open core file
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 10 16:10:26 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Andriy Gapon
>Release:        FreeBSD 6.1-RELEASE-p2 i386
>Organization:
>Environment:
System: 
FreeBSD 6.1-RELEASE-p2 i386
kdbg-2.0.4
	
>Description:
if kdbg is started as 'kdbg program core' or core file is opened through gui menu,
then kdbg actually fails to open the core file with the following error:
GDB: Undefined target command: "core xxxxx.core". Try "help target".

The message obviously comes from gdb(1).
"help target" in gdb on my system produces:
List of target subcommands:

target FreeBSD-core -- FreeBSD threads support for core files
target async -- Use a remote computer via a serial line
target child -- Unix child process (started by the "run" command)
target exec -- Use an executable file as a target
target extended-async -- Use a remote computer via a serial line
target extended-remote -- Use a remote computer via a serial line
target freebsd-threads -- FreeBSD threads support
target remote -- Use a remote computer via a serial line

As you can see "core" target is indeed missing here. Not sure if this is gdb's fault,
but I suspect that kdbg should use "target FreeBSD-core" instead of "target core".

>How-To-Repeat:
run the following:
kdbg some_program core_file

>Fix:

	


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list