bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bash printf should diagnose integer overflow


From: Paul Eggert
Subject: Re: Bash printf should diagnose integer overflow
Date: Thu, 21 Mar 2024 23:40:14 -0700
User-agent: Mozilla Thunderbird

On 2024-03-21 13:31, Chet Ramey wrote:

Interesting. I can't reproduce this. Using the commit to which your patches
apply, without applying any of them, on a fresh Virtualbox Fedora 39
install, I get consistent `make tests' output every time.

I just now tried the latest devel commit (b1e7f68032bd90dec1a2968a616b32a469929c78) on Fedora 39 running on bare hardware (AMD Phenom II X4 910e), with Fedora patches up through today and with 873 locales installed (output of "locale -a | wc"). Often "make check" output was the same, but sometimes it differed. Here's the first difference (after this I stopped checking):

$ diff -u :check[34].log
--- :check3.log 2024-03-21 14:09:48.069094929 -0700
+++ :check4.log 2024-03-21 22:39:51.391869014 -0700
@@ -327,6 +327,10 @@
 warning: UNIX versions number signals and schedule processes differently.
 warning: If output differing only in line numbers is produced, please
 warning: do not consider this a test failure.
+111c111
+< ./trap8.sub: DEBUG warning: run_pending_traps: recursive invocation while 
running trap for signal 17
+---
+> CHLD
 run-type
 run-varenv
 warning: some of these tests will fail if arrays have not

I recall other differences in past runs.


Output that differs in error message language isn't a failure.

Yes, and I assumed that since output like the above didn't affect the exit status of "make check", it wasn't that important.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]