C01arith.ztst

C01arith.ztst

[Clint Adams]

> Yup, working on RHEL (actually CentOS, but they should be equivalent).

I don't have any problems with C03traps, but I notice

Test ../../Test/C01arith.ztst failed: bad status 1, expected 0 from:
  print $((##))
Error output:
(eval):1: bad math expression: illegal character: ^P
Was testing: ## without following character

on at least two of our mips autobuilders.

http://buildd.debian.org/fetch.php?&pkg=zsh&ver=4.2.0-10&arch=mips&stamp=1084382326&file=log&as=raw
http://buildd.debian.org/fetch.php?&pkg=zsh-beta&ver=4.2.0-dev-1%2B20040512-1&arch=mips&stamp=1084379509&file=log&as=raw

Any idea what this means?

Re: C01arith.ztst

[Peter Stephenson]

Clint Adams wrote:
> > Yup, working on RHEL (actually CentOS, but they should be equivalent).
> 
> I don't have any problems with C03traps, but I notice
> 
> Test ../../Test/C01arith.ztst failed: bad status 1, expected 0 from:
>   print $((##))
> Error output:
> (eval):1: bad math expression: illegal character: ^P
> Was testing: ## without following character

Suggests some problem with tokenisation or parsing.  Should be
relatively easy to trace by hand, if it's tied to the command and not
the environment.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: C01arith.ztst

[Clint Adams]

> Suggests some problem with tokenisation or parsing.  Should be
> relatively easy to trace by hand, if it's tied to the command and not
> the environment.

The string stored at ptr, after ptr is no longer equal to optr, changes
from "" to "\020" when checkunary() is called.  I'm going to try again
with gcc -O0 to see if the same thing happens.

Re: C01arith.ztst

[Clint Adams]

> The string stored at ptr, after ptr is no longer equal to optr, changes
> from "" to "\020" when checkunary() is called.  I'm going to try again
> with gcc -O0 to see if the same thing happens.

The test passes with no optimization; I guess this means it's a gcc bug
specific to mips.

Re: C01arith.ztst

[Falk Hueffner]

Clint Adams <clint@zsh.org> writes:

>> The string stored at ptr, after ptr is no longer equal to optr, changes
>> from "" to "\020" when checkunary() is called.  I'm going to try again
>> with gcc -O0 to see if the same thing happens.
>
> The test passes with no optimization; I guess this means it's a gcc
> bug specific to mips.

Please file a bug report with a test case, then.

-- 
	Falk