NetBSD Problem Report #381

From gnats  Tue Aug  2 18:59:45 1994
Received: from uwm.edu (uwm.edu [129.89.6.2]) by sun-lamp.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id SAA00320 for <gnats-bugs@sun-lamp.cs.berkeley.edu>; Tue, 2 Aug 1994 18:59:40 -0700
Message-Id: <199408030158.UAA21019@enigma.cs.uwm.edu>
Date: Tue, 2 Aug 1994 20:58:29 -0500
From: James Jegers <jimj@enigma.cs.uwm.edu>
Reply-To: jimj@enigma.cs.uwm.edu
To: gnats-bugs@sun-lamp.cs.berkeley.edu
Subject: gdb can't do core files
X-Send-Pr-Version: 3.2

>Number:         381
>Category:       bin
>Synopsis:       gdb can't do core files
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 02 19:05:01 +0000 1994
>Closed-Date:    Wed Aug 03 07:59:14 +0000 1994
>Last-Modified:  
>Originator:     James Jegers
>Release:        
>Organization:
"	"
>Environment:

System: NetBSD enigma.cs.uwm.edu 1.0beta ENIGMA#1 i386


>Description:

	gdb can't examine core files anymore.
	You can run gdb on a execuatable and examine it after it core
	dumpgs, but you cann't examine a core dump file.
	gdb says unknown file type.
>How-To-Repeat:
	write a program which crashes, and creates a core file, run gdb on it.
	gdb -core a.out.core   or
	gdb a.out a.out.core  or
	gdb a.out.core

	all of these say a.out.core unknown type of core file(or similar).

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: mycroft 
State-Changed-When: Wed Aug 3 00:59:14 PDT 1994 
State-Changed-Why:  
This simply does not happen on newly-installed systems.  It seems very 
likely to be user error. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.