Re: stdioext OpenVMS patch.

Hi John, > On OpenVMS, the struct _iobuf is needed to access members of the struct > FILE. > > This is a patch for the affected stdioext modules to compile on OpenVMS. The approach looks generally right, but I'd request a couple of changes before this can go in: * Is _IOERR defined on OpenVM

Re: Memleak in glob()

Hi Tim, > Attached is a patch fixing the issue for me The 'return 0;' in line 1104 is correct, because 'dirname' is stuffed into the result array in the lines before. Therefore dirname must NOT be freed here. For the other ones, you may be right, but I wonder why scan.coverity.com did not displa

stdioext OpenVMS patch.

On OpenVMS, the struct _iobuf is needed to access members of the struct FILE. This is a patch for the affected stdioext modules to compile on OpenVMS. Regards, -John 0001-stdioext-Port-to-OpenVMS.patch.gz Description: GNU Zip compressed data

Memleak in glob()

Hi, fuzzing glob.c immediately discovered a leak. At ~L600 in glob.c, 'dirname' is heap allocated. It is free'd at label 'out', but some code paths directly return without jumping there. Attached is a patch fixing the issue for me, but just take it as a proof of concept. You might prefer a diffe

testing on sh4 hardware?

Hi, Does someone have access to sh4 hardware and could test gnulib on sh4-linux? With qemu-sh4 and glibc-2.23, I'm seeing a couple of worrisome test failures: FAIL: test-lock === Starting test_lock ...test-lock: pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__da

workaround glibc bug in logbl()

On Linux/PowerPC64LE, with glibc-2.23 (under qemu), I'm seeing this gnulib test failure: FAIL: test-logbl ../../gltests/test-logb.h:94: assertion 'y == (DOUBLE)(i - 1)' failed qemu: uncaught target signal 6 (Aborted) - core dumped When I add an fprintf statement there: fpr