🚀 go-pugleaf

Both of these bugs are in gdb 3.5.3 running on bsd on an hp 68020
system.

I was debugging cc1, and did pt on a value that was not a valid
tree node.  It crashed, and I used the return command to get rid
of the stack frames made by pt.  Later I tried pt again, and it
refused to even try to run the function call.

Later on, I had a breadpoint in mul_double, and stepped to  line 250.
There the value of l1 was 0x90000000 while that of temp was 0x20000000.
I did `p temp<l1'.  The value was 0.  It seems that gdb did a signed
comparison when it should have been unsigned.