bug#68708: [PATCH] env,kill: Handle unnamed signals

2024-01-24 Thread Grisha Levit
Android reserves [1] some realtime signals and redefines [2] SIGRTMIN, leaving a gap between the signals that have SIG* constants defined in signal.h and SIGRTMIN. When passed such a signal number, gnulib sig2str returns -1 and leaves its signame argument unchanged. The signal listing in env ends

bug#68707: [PATCH] env,kill: Handle unnamed signals

2024-01-24 Thread Grisha Levit
Android reserves [1] some realtime signals and redefines [2] SIGRTMIN, leaving a gap between the signals that have SIG* constants defined in signal.h and SIGRTMIN. When passed such a signal number, gnulib sig2str returns -1 and leaves its signame argument unchanged. The signal listing in e

bug#68708: [PATCH] env,kill: Handle unnamed signals

2024-01-25 Thread Grisha Levit
> On Thu, Jan 25, 2024, 09:50 Pádraig Brady wrote: > This mostly looks good, except: > > - No need to clear the errno before kill(3). > - Better to use SIG%d rather than the bare %d for signal _names_, as we > already parse this format Makes sense, done below. * src/operand2sig.c (operand2sig)

bug#69770: [PATCH] build: strengthen 16 bit float support checks

2024-03-12 Thread Grisha Levit
Recent clang provides __bf16 on aarch64 but it is broken. If built with -O0, the conversion is wrong: $ printf '\x3F\x80' | od --end=big -An -tfB | tr -d ' ' 1.875 If built with -O1 or higher, compilation fails: fatal error: error in backend: Cannot select: 0xb47a58d29780: f32 =

bug#74428: tests/printf/printf-cov failure on macOS

2024-11-18 Thread Grisha Levit
The u4 and U8 tests in tests/printf/printf-cov.pl fail on macOS 15: u4... printf: test u4: stdout mismatch, comparing u4.1 (expected) and u4.O (actual) *** u4.1Mon Nov 18 23:30:03 2024 --- u4.OMon Nov 18 23:30:03 2024 *** *** 1 ! 0 \ No newline at end of file --- 1

bug#74426: tests/dd/skip-seek-past-file failure on macOS

2024-11-18 Thread Grisha Levit
tests/dd/skip-seek-past-file.sh fails on macOS 15 when checking for a warning being printed when seeking past the max file size [1]. Reproducing outside the test suite: $ > file $ dd bs=1 skip=9223372036854775807 count=0 status=noxfer < file 0+0 records in 0+0 records out $ echo $? 0 Note that i

bug#74427: tests/printf/printf-indexed failure on macOS

2024-11-18 Thread Grisha Levit
See the following two chunks from the test suite log on macOS 15: + printf_check ' 0 1 ' '%100$*d %s %s %s\n' 4 1 + cat + shift + env printf '%100$*d %s %s %s\n' 4 1 printf: '': Invalid argument + fail=1 + printf_check_err 'printf: '\''A'\'': expected a numeric value' '%0x2$s %2$s\n' A B + ca

bug#78880: od Heap-buffer overflow

2025-06-24 Thread Grisha Levit
On Tue, Jun 24, 2025, 10:04 Pádraig Brady wrote: > > On 24/06/2025 01:16, Pádraig Brady wrote: > > On 23/06/2025 09:24, Jaehoon Jang wrote: > >> = > >> ==1151699==ERROR: AddressSanitizer: heap-buffer-overflow on address > >> 0x615

bug#78880: od Heap-buffer overflow

2025-06-27 Thread Grisha Levit
On Tue, Jun 24, 2025, 12:34 Collin Funk wrote: > > Pádraig Brady writes: > > > On 24/06/2025 15:27, Grisha Levit wrote: > > > >> This part: > >> > >>> tryline: > >>> + idx_t i = 0; > >>> +

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Grisha Levit
On Fri, Jul 25, 2025, 12:02 Stan Marsh wrote: > > I used the following command to check disk usage in ~: > > $ du -sxc ~/* > > Unfortunately, this hung when it hit the directory ~/sshfs_mount, which is > sshfs > mounted to my home dir on some other system. > When the glob is expanded, $HOME/ssh