[Top][All Lists]

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

Re: Segfault on $(file > bug)

From: Andreas Freimuth
Subject: Re: Segfault on $(file > bug)
Date: Sun, 31 May 2015 01:22:38 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

On 30.05.2015 19:53, Paul Smith wrote:
> On Mon, 2015-05-25 at 19:02 +0200, Andreas Freimuth wrote:
>> make segfaults after a
>>  $(file > bug)
>> statement.
>> How to reproduce:
>> $ mkdir /tmp/makeBUG && cd /tmp/makeBUG
>> $ echo '$(file > bug)' > makefile
>> $ make
>> Tested with:
>> GNU Make 4.0
>> Built for x86_64-redhat-linux-gnu
> In GNU make 4.0, that statement was invalid.  You always had to provide
> a second argument containing something to write to the file (it could be
> empty).  If you use:
>   $ echo '$(file > bug,)' > makefile
> (note added comma after bug) then you'd get expected behavior with no
> core dump.  Of course, the core dump was obviously a bug.
I know, this comes pretty close to what i want, except the new line.

>> GNU Make 4.1
>> Built for x86_64-unknown-linux-gnu
> In GNU make 4.1, it is now legal to simply omit the argument altogether.
> I don't see any core dump in this version; please verify that you're
> really running GNU make 4.1 when you see this problem.  See the NEWS
> file for 4.1:
>> * Allow a no-text-argument form of the $(file ...) function.  Without a
>>   text argument nothing is written to the file: it is simply opened in the
>>   requested mode, then closed again.

Your probably right. Can not reproduce it with make-4.1 either. And
bash-history indicates that I might have missed '/usr/local/bin/' some
times when I was testing the latest release.

Thanks and sorry for the noise.

Andreas Freimuth

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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