From rcarter@geli.com Sun Mar 19 16:28:06 1995 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA26760 for ; Sun, 19 Mar 1995 16:28:05 -0800 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.11/8.6.5) with ESMTP id QAA01738 for ; Sun, 19 Mar 1995 16:27:43 -0801 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id QAA00668; Sun, 19 Mar 1995 16:26:57 -0800 Message-Id: <199503200026.QAA00668@geli.clusternet> Date: Sun, 19 Mar 1995 16:26:57 -0800 From: rcarter@geli.com Reply-To: rcarter@geli.com To: FreeBSD-gnats-submit@freebsd.org Subject: nasty gdb bug back in 031595 system X-Send-Pr-Version: 3.2 >Number: 256 >Category: gnu >Synopsis: nasty gdb bug back in 031595 system >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Mar 19 16:30:01 1995 >Closed-Date: Thu Feb 8 08:24:00 PST 1996 >Last-Modified: Tue Nov 27 18:41:46 PST 2001 >Originator: Russell L. Carter >Release: FreeBSD 2.1.0-Development i386 031595 >Organization: Geli Engineering >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 >Release-Note: >Audit-Trail: State-Changed-From-To: open->closed State-Changed-By: wollman State-Changed-When: Thu Feb 8 08:24:00 PST 1996 State-Changed-Why: This bug is a bit stale. If the problem remains, please submit a new problem report. >Unformatted: