This bug was fixed in the package gawk - 1:3.1.6.dfsg-0ubuntu1
---
gawk (1:3.1.6.dfsg-0ubuntu1) hardy; urgency=low
* New upstream version.
- Remove patches applied upstream: 01_po-Makefile.in.in.dpatch,
19_io.c-invalid-free.dpatch, 20_eval.c-utf-8-strcat.dpatch,
25_f
I can confirm the problem. I've had awk scripts fail mysteriously due to
this bug on amd64. The current upstream release (3.1.6) has this fixed.
To be honest, I'm surprised this hasn't broken all kinds of stuff on my
system -- is awk not widely used for configuration, etc?
--
match operator brok
(If it is inappropriate for me to change status, feel free to revert.)
** Changed in: gawk (Ubuntu)
Status: New => Confirmed
--
match operator broken on amd64
https://bugs.launchpad.net/bugs/127850
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
Further examination reveals this to be a problem with the handling of
multibyte characters. It was working in my x86 chroot owing to
different locale settings.
builtin.c has the following:
#ifdef MBS_SUPPORT
if (gawk_mb_cur_max > 1) {
t1 = str2wstr(t1, & w
** Description changed:
The match operator returns an invalid result and fails to correctly set
- RSTART and RLENGTH on an unsuccessful match.
+ RSTART and RLENGTH on an empty match.
Test case courtesy of Alain Ketterlin on the bug-gnu-utils mailing list
at http://lists.gnu.org/archive/ht
