[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FAIL: autopoint-3
From: |
Santiago Vila |
Subject: |
Re: FAIL: autopoint-3 |
Date: |
Sat, 22 Jun 2024 12:31:45 +0200 |
User-agent: |
Mozilla Thunderbird |
El 22/6/24 a las 1:05, Bruno Haible escribió:
Santiago Vila wrote:
So, yes, this is most probably a memory-handling bug in mawk.
Can you debug it? I don't think valgrind is needed; simply recompiling
the mawk binary with clang + ASAN + UBSAN should reveal the relevant stack
traces.
So far, GNU been stating that any 'awk' implementation is sufficient
for executing configure scripts. I wouldn't like to have to remove 'mawk'
from the list of possible choices.
I agree.
Fortunately, that will not be necessary, as I bisected the bug yesterday
and found that the bug exists since version 20231101, so I told the
upstream mawk maintainer (Thomas Dickey) about it, and he suggested
this fix:
https://github.com/ThomasDickey/original-mawk/issues/77
which fixes my issue as well, so there is actually nothing to debug.
For the Debian package, I still will have to add something like this
to the build-depends:
gawk | mawk (>= fixed-version)
at least for trixie, because that's better than disabling a test.
Thanks.