Re: strstr (was: test-memchr crash)

Eric Blake wrote: > Hmm. I'm now starting to wonder whether I should create a new module > strstr-simple, which fixes broken strstr (in the presence of broken > memchr) but without worrying about quadratic vs. linear (similar to > strcasestr-simple which only worries about providing strcasestr on

strstr (was: test-memchr crash)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 6/16/2009 6:16 AM: > Oh. That's because your strstr is already non-linear (your glibc 2.7 is > older than when they picked up my strstr implementation, around Feb 2008 > and glibc 2.9). So there's only a narrow window of ti

Re: test-memchr crash

Simon Josefsson writes: > I have started a build of gnulib on that host, and it will run daily > from now on. First build was successful: http://autobuild.josefsson.org/gnulib/log-200906160813476137000.txt Btw, speaking generally, powerpc-apple-darwin8.11.0 is close to passing a build. The onl

Re: test-memchr crash

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Simon Josefsson on 6/16/2009 1:30 AM: > checking whether strstr works in linear time... no > ... > PASS: test-strstr > > I checked, and the gnulib strstr replacement is used. Oh. That's because your strstr is already non-linear (your gl

Re: test-memchr crash

Eric Blake writes: > According to Simon Josefsson on 6/13/2009 10:43 AM: >>> Looks pretty much like one of the glibc memchr bugs that were recently >>> fixed: >>> >> >> I'm not sure, the machine where this fails runs glibc 2.7 and the bug

Re: test-memchr crash

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Simon Josefsson on 6/13/2009 10:43 AM: >> Looks pretty much like one of the glibc memchr bugs that were recently fixed: >> > > I'm not sure, the machine where this fails runs glibc

Re: test-memchr crash

Eric Blake wrote: > I've had this sitting around for a while [1], so now that we have > confirmed this is a problem in a wild, I'm committing it. Very nice! I'm adding a mention of the ia64 specific bug that Simon encountered. 2009-06-14 Bruno Haible * m4/memchr.m4: Mention also the

Re: test-memchr crash

Eric Blake writes: > According to Bruno Haible on 6/12/2009 6:33 AM: >> Looks pretty much like one of the glibc memchr bugs that were recently fixed: >> >> >> So, it was a good move to un-obsolete the 'memchr' module. But now we also >> n

Re: test-memchr crash

Bruno Haible writes: > Simon Josefsson wrote: >> test-memchr appears to crash on a ia64-unknown-linux-gnu system: > ... >> #1 0x40002140 in main () at test-memchr.c:119 >> i = 0 >> mem = 0x206d3ff8 "UXXX" >> n = 8 >> page_boundary = 0x206d4000 "" >

Re: test-memchr crash

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 6/12/2009 6:33 AM: > Looks pretty much like one of the glibc memchr bugs that were recently fixed: > > > So, it was a good move to un-obsolete the 'memchr' module. B

Re: test-memchr crash

Simon Josefsson wrote: > test-memchr appears to crash on a ia64-unknown-linux-gnu system: ... > #1 0x40002140 in main () at test-memchr.c:119 > i = 0 > mem = 0x206d3ff8 "UXXX" > n = 8 > page_boundary = 0x206d4000 "" Looks pretty much like one of

test-memchr crash

test-memchr appears to crash on a ia64-unknown-linux-gnu system: http://autobuild.josefsson.org/gsasl/log-200906120502710714000.txt Here is a backtrace: (gdb) r Starting program: /home/jas/gsasl/gsasl-1.2/lib/gltests/test-memchr [Thread debugging using libthread_db enabled] [New Thread 0x20