🚀 go-pugleaf

I found a bug in the gdb command `cond'. This is how to reproduce it:

- create a file, say test.c, with the following contents:
/* a very silly test program */
int y;

main()
{
    a(1);
}

a(x)
{
   y = x;
}

- compile this file with -g option producing executable test
- run gdb
- type in the commands as in the following typescript:
GDB 3.3, Copyright (C) 1989 Free Software Foundation, Inc.
There is ABSOLUTELY NO WARRANTY for GDB; type "info warranty" for details.
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "info copying" to see the conditions.
Type "help" for a list of commands.
(gdb) exec test
(gdb) sym test
Reading symbol data from /home/arwen/pgs/pg167/schwab/test/test...done.
(gdb) break main
Reading in symbols for test.c...done.
Breakpoint 1 at 0x2294: file test.c, line 5.
(gdb) cond 1 y == 0
(gdb) cond 1 x == 0
No symbol "x" in current context.
(gdb) cond 1 y == 0
gdb: free: Called with already freed block argument

Quit

--
Andreas Schwab			schwab@ls5.informatik.uni-dortmund.de
University of Dortmund		schwab%ls5@unido.uucp, schwab%ls5@unido.bitnet
[West-]Germany			{uunet,mcvax}!unido!julien!schwab