[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <3DD147FE-6B27-41BB-8C09-4F569D62F74B@chuckremes.com>
Date: Sat, 11 Feb 2017 17:28:37 -0600
From: lists@...ckremes.com
To: musl@...ts.openwall.com
Subject: behavior errata
While debugging an issue where a child process’s errno was getting clobbered, discovered that musl was doing the clobbering in a call to strftime (that did NOT fail).
I understand the contract of libc calls is that errno can be clobbered at any time. However, it’s a behavior difference between musl and other libc’s that I have tested against.
Here’s the repro code.
https://gist.github.com/chuckremes/698b0ee5d1279374cb1ef3add82a6f18
I had a nice chat with some folks on IRC about this. They indicated that it might get “fixed” just to be nice but there is no requirement to do so. Someone even made the (evil but funny) suggestion that musl should clobber errno between every non-failing call just to see how much code in the wild would explode. Please don’t. :)
Thanks for your attention.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
