Date: Sun, 10 Sep 2023 13:06:36 +0000 From: Lorenzo Salvadore <developer@lorenzosalvadore.it> To: Warner Losh <imp@bsdimp.com> Cc: Robert Clausecker <fuz@fuz.su>, FreeBSD Current <current@freebsd.org> Subject: Re: sed in CURRENT fails in textproc/jq Message-ID: <0uCAJNKOmP1ftVb8nkaEqKL7B1F8w5PXxHRrSvTVY70xHnF4f2J8k8QNGnwkMWnq8GgSgCDc7Kp27RNKjvZnkDsQdpNpDKqDxlCrkcpfGvE=@lorenzosalvadore.it> In-Reply-To: <CANCZdfpesLu%2B5YLB4-irR7XSSSM1wXPLH58TbefPzvGo=q1xgg@mail.gmail.com> References: <30a59ac0-28fd-f6ed-505c-9ef6d8e84fc3@tsoft.com> <CAALwa8kAaDw80h2cbaeLOmw2G9EpRo6dJFZcFFc99mAU_7xkRA@mail.gmail.com> <86edj7qnia.fsf@ltc.des.no> <ZP1LPZcC99zIS1Jp@fuz.su> <CANCZdfpesLu%2B5YLB4-irR7XSSSM1wXPLH58TbefPzvGo=q1xgg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------- Original Message ------- On Sunday, September 10th, 2023 at 13:51, Warner Losh <imp@bsdimp.com> wrot= e: >=20 >=20 > On Sat, Sep 9, 2023, 10:51 PM Robert Clausecker <fuz@fuz.su> wrote: >=20 > > Greetings, > >=20 > > I apologise for the inconvenience. The issue seems to boil down to > > various places calling > >=20 > > memchr(buf, c, SIZE_MAX); > >=20 > > which causes an overflow when my newly written memchr() computes buf + > > len to find the end of the buffer. A patch to alleviate this issue can > > be found here: > >=20 > > http://fuz.su/~fuz/freebsd/0001-lib-libc-amd64-string-memchr.S-fix-beha= viour-with-ov.patch > >=20 > > Please check if it does the trick for you. If yes, I'll go ahead and > > push it tomorrow-ish. >=20 >=20 >=20 > There are half a dozen or do kyua tests that are likely failing because o= f this or other reasons related to strings. When you push this fix you'll g= et the list. They are hidden among about 80 or so networking tests that fai= l. I plan on disabling those tests soon If no one fixes them. >=20 > Warner >=20 > >=20 > > Yours, > > Robert Clausecker > >=20 > > Am Sat, Sep 09, 2023 at 07:12:29PM +0200 schrieb Dag-Erling Sm=C3=B8rgr= av: > > > Antoine Brodin <antoine@freebsd.org> writes: > > > > Yuri <yuri@freebsd.org> writes: > > > > > Either something has changed in sed(1) in CURRENT, or sed just fa= ils > > > > > during the configure stage of textproc/jq: > > > > > > > > > > sed: No error: 0 > > > > > checking for sys/cygwin.h... eval: ${+...}: Bad substitution > > > > This seems to be a recent issue (less than 5 days). > > > > Hundreds of configure scripts now fail to run on 15-current due to > > > > this sed failure: [...] > > > > > > Try adding ARCHLEVEL=3Dscalar to CONFIGURE_ENV on one of these. If th= at > > > helps, yell at fuz@ :) > > > > > > DES > > > -- > > > Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org > > > > >=20 > > -- > > () ascii ribbon campaign - for an 8-bit clean world > > /\ - against html email - against proprietary attachments > >=20 The issue seems to also affect lang/gcc14-devel: https://pkg-status.freebsd.org/beefy18/data/main-amd64-default/pe88937b01dd= 4_s3482f57f0f/logs/gcc14-devel-14.0.0.s20230903.log Cheers, Lorenzo Salvadore
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0uCAJNKOmP1ftVb8nkaEqKL7B1F8w5PXxHRrSvTVY70xHnF4f2J8k8QNGnwkMWnq8GgSgCDc7Kp27RNKjvZnkDsQdpNpDKqDxlCrkcpfGvE=>