grep-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Grep-devel] [platform-testers] new snapshot available: grep-3.1.46-


From: Bruno Haible
Subject: Re: [Grep-devel] [platform-testers] new snapshot available: grep-3.1.46-504af
Date: Sun, 16 Dec 2018 15:56:19 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-139-generic; KDE/5.18.0; x86_64; ; )

I wrote:
> In details: I reproduce the issue on gcc113.fsffrance.org (a Linux/aarch64
> machine) in 64-bit mode.
> That is, the test fails with 'grep never printed "stack overflow"'. But
> when I run the commands interactively, grep prints "stack overflow" already
> at the second round:
> 
> $ printf %010000d 0 | tr 0 '(' > in ; ./grep -E -f in
> ./grep: in:1: Unmatched ( or \(
> $ printf %020000d 0 | tr 0 '(' > in ; ./grep -E -f in
> grep: stack overflow
> 
> So added an 'ulimit -a > ulimit.out' command in the test, and the result is
> 
> stack size              (kbytes, -s) unlimited
> 
> which is different than what I have in my interactive environment:
> 
> stack size              (kbytes, -s) 8192
> 
> So probably 'make' or '/bin/sh' must be resetting the stack size.

The exact same thing happens on a Linux/alpha machine (running Debian 5.0.10).
The fix, here as well, is to insert a statement

  ulimit -s 8192 2>/dev/null

near the top of the tests/stack-overflow file.

Bruno




reply via email to

[Prev in Thread] Current Thread [Next in Thread]