From owner-freebsd-bugs Mon Jul 5 1:20: 3 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 77D8514CAF for ; Mon, 5 Jul 1999 01:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA85493; Mon, 5 Jul 1999 01:20:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 5 Jul 1999 01:20:01 -0700 (PDT) Message-Id: <199907050820.BAA85493@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/10064: /bin/sh called from make dumps core Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/10064; it has been noted by GNATS. From: Sheldon Hearn To: Juergen Lock Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/10064: /bin/sh called from make dumps core Date: Mon, 05 Jul 1999 10:19:13 +0200 On Sun, 04 Jul 1999 12:44:15 +0200, Juergen Lock wrote: > Hmm so let's find out which patch makes it dissapear. After building > several sh:s from the RELENG_2_2 branch i found out the 2.2.7R sh > dies and the 2.2.8R sh doesn't, and the crucial patch is in parser.c > (0parser228 below). undoing that patch in the 3.2-stable sh as well > as in the -current sh cause both to crash, and that patch doesn't > look like it could fix a stack bug, only mask it by using the stack > differently, right? Surely one way to fix a stack bug is to use the stack differently? :-) I think the important thing, as you've discovered for yourself, is that it's fixed in 2.2.8-RELEASE, 3.2-STABLE and 4.0-CURRENT. Thanks for the feedback. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message