From owner-freebsd-bugs  Sun Mar 19 16:30:03 1995
Return-Path: bugs-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA26984 for bugs-outgoing; Sun, 19 Mar 1995 16:30:03 -0800
Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA26972; Sun, 19 Mar 1995 16:30:02 -0800
Date: Sun, 19 Mar 1995 16:30:02 -0800
Message-Id: <199503200030.QAA26972@freefall.cdrom.com>
From: rcarter@geli.com
Reply-To: rcarter@geli.com
To: freebsd-bugs
Subject: gnu/256: nasty gdb bug back in 031595 system
In-Reply-To: Your message of Sun, 19 Mar 1995 16:26:57 -0800
	<199503200026.QAA00668@geli.clusternet>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         256
>Category:       gnu
>Synopsis:       nasty gdb bug back in 031595 system
>Confidential:   yes
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 19 16:30:01 1995
>Originator:     Russell L. Carter
>Organization:
Geli Engineering
>Release:        FreeBSD 2.1.0-Development i386 031595
>Environment:

	P5-90, 32MB, ncr pci...

>Description:

	gdb hangs the system hard when a program being debugged
        is run.  Only does this on one large package.  I'm trying
	to find a small enough example to forward, but no success
	so far.

>How-To-Repeat:

	gdb program-name
	run

>Fix:
	
	none known

>Audit-Trail:
>Unformatted: