public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/70493] std::setlocale("") throws exception
       [not found] <bug-70493-4@http.gcc.gnu.org/bugzilla/>
@ 2020-07-13 11:15 ` redi at gcc dot gnu.org
  0 siblings, 0 replies; only message in thread
From: redi at gcc dot gnu.org @ 2020-07-13 11:15 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70493

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Libstdc++ has no idea why the locale name was invalid. When you use the empty
string "" it constructs a locale name from the environment and then calls
newlocale from the C library. newlocale returns (locale_t)0 and sets ENOENT,
which according to POSIX means "For any of the categories in category_mask, the
locale data is not available" (or for the GNU C library, "locale is not a
string pointer referring to a valid locale").

Unless libstdc++ is going to iteratively try creating a locale from each of the
LC_* environment variables to see which one failed, it can't really give you
any better information. That doesn't seem worth the effort (and increase in
code size), sorry.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-07-13 11:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-70493-4@http.gcc.gnu.org/bugzilla/>
2020-07-13 11:15 ` [Bug libstdc++/70493] std::setlocale("") throws exception redi at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).