From owner-freebsd-current@FreeBSD.ORG  Mon Jun 11 01:57:52 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: by hub.freebsd.org (Postfix, from userid 680)
	id 03CDB16A468; Mon, 11 Jun 2007 01:57:52 +0000 (UTC)
Date: Mon, 11 Jun 2007 01:57:52 +0000
From: Darren Reed <darrenr@freebsd.org>
To: current@freebsd.org
Message-ID: <20070611015752.GA82125@hub.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Cc: 
Subject: yacc/gdb issues with 7.0-current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2007 01:57:52 -0000

Using 7.0-current from around May 20, a couple of things I've run
across today...

gdb seems to have "issues" in -current after doing "run".
The output below is from truss on gdb's pid:
...
kill(15590,0)                                    = 0 (0x0)
ptrace(0x21,0x3ce6,0xbfbfdc70,0x0,0x28277130)    = 0 (0x0)
ptrace(0x25,0x3ce6,0xbfbfddb4,0x0,0x8)           = 0 (0x0)
ptrace(0x7,0x3ce6,0x1,0x14,0x10202)              = 0 (0x0)
wait4(0xffffffff,0xbfbfdee8,0x0,0x0,0x28369569)  = 15590 (0x3ce6)
kill(15590,0)                                    = 0 (0x0)
ptrace(0x21,0x3ce6,0xbfbfdc70,0x0,0x28277130)    = 0 (0x0)
ptrace(0x25,0x3ce6,0xbfbfddb4,0x0,0x8)           = 0 (0x0)
ptrace(0x7,0x3ce6,0x1,0x14,0x10202)              = 0 (0x0)
wait4(0xffffffff,0xbfbfdee8,0x0,0x0,0x28369569)  = 15590 (0x3ce6)
kill(15590,0)                                    = 0 (0x0)
ptrace(0x21,0x3ce6,0xbfbfdc70,0x0,0x28277130)    = 0 (0x0)
ptrace(0x25,0x3ce6,0xbfbfddb4,0x0,0x8)           = 0 (0x0)
ptrace(0x7,0x3ce6,0x1,0x14,0x10202)              = 0 (0x0)
wait4(0xffffffff,0xbfbfdee8,0x0,0x0,0x28369569)  = 15590 (0x3ce6)
kill(15590,0)                                    = 0 (0x0)
ptrace(0x21,0x3ce6,0xbfbfdc70,0x0,0x28277130)    = 0 (0x0)
ptrace(0x25,0x3ce6,0xbfbfddb4,0x0,0x8)           = 0 (0x0)
ptrace(0x7,0x3ce6,0x1,0x14,0x10202)              = 0 (0x0)
wait4(0xffffffff,0xbfbfdee8,0x0,0x0,0x28369569)  = 15590 (0x3ce6)
kill(15590,0)                                    = 0 (0x0)
ptrace(0x21,0x3ce6,0xbfbfdc70,0x0,0x28277130)    = 0 (0x0)
ptrace(0x25,0x3ce6,0xbfbfddb4,0x0,0x8)           = 0 (0x0)
...

The other issue I've found is with yacc - it core dumps rather than
reports an error about not returning/assign a value.

e.g. if I do:
%type <foo>	bar
...
bar:	| 'x' { $$ = getbar('x'); }
	;
...

it should give me an error but instead I got a core dump.
The correct yacc input is:
bar:	{ $$ = 0; } | 'x' { $$ = getbar('x'); }
	;

Darren