From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [PATCH] Gracefully handle incompatible locale data Date: Thu, 24 Sep 2015 18:12:37 +0200 Message-ID: <87h9mjeqyy.fsf@gnu.org> References: <876132lbic.fsf@gnu.org> <20150922191804.GA13637@domone> <877fnijgin.fsf@gnu.org> <20150922215022.GA27201@domone> <8737y4hkrz.fsf@gnu.org> <20150924082755.GA4767@domone> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <20150924082755.GA4767@domone> (=?utf-8?Q?=22Ond=C5=99ej_B?= =?utf-8?Q?=C3=ADlka=22's?= message of "Thu, 24 Sep 2015 10:27:55 +0200") To: =?utf-8?B?T25kxZllaiBCw61sa2E=?= Cc: libc-alpha@sourceware.org, guix-devel@gnu.org List-Id: guix-devel.gnu.org Ond=C5=99ej, I think we have been miscommunicating. I noticed that a program linked against 2.21 or earlier would abort with an assertion failure when it stumbles upon 2.22 locale data. All the patch tries to do is change the abort to EINVAL (and skip locale data) when that happens. I=E2=80=99m not claiming this is perfect, and I agree with you on that poin= t. I=E2=80=99m just saying that ignoring the faulty locale data and returning EINVAL (which the application can choose to take into account or not) is preferable to aborting. Does that make sense? Thanks, Ludo=E2=80=99.