From owner-freebsd-current  Thu May 25 22:59:44 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id WAA15352
          for current-outgoing; Thu, 25 May 1995 22:59:44 -0700
Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA15346
          for <current@freebsd.org>; Thu, 25 May 1995 22:59:42 -0700
Received: (from root@localhost) by sbstark.cs.sunysb.edu (8.6.12/8.6.9) with UUCP id BAA08506 for current@freebsd.org; Fri, 26 May 1995 01:59:01 -0400
Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.6.11/8.6.9) id BAA13019; Fri, 26 May 1995 01:59:11 -0400
Date: Fri, 26 May 1995 01:59:11 -0400
From: Gene Stark <gene@starkhome.cs.sunysb.edu>
Message-Id: <199505260559.BAA13019@starkhome.cs.sunysb.edu>
To: current@FreeBSD.org
Subject: gdb broken (can't find stack)
Sender: current-owner@FreeBSD.org
Precedence: bulk

For my May 20 compiled gdb, I just observed that it couldn't find a stack
in a core dump file, though it seemed to be able to do it when tracing
an inferior:

	gdb a.out
	(gdb) bt
	No stack.

Was there a change that broke this?  It was working a few weeks ago.

							- Gene