public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast
       [not found] <bug-82366-4@http.gcc.gnu.org/bugzilla/>
@ 2023-10-27  4:13 ` a1ba.omarov at gmail dot com
  2023-10-27  6:41 ` redi at gcc dot gnu.org
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 6+ messages in thread
From: a1ba.omarov at gmail dot com @ 2023-10-27  4:13 UTC (permalink / raw)
  To: gcc-bugs

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

Alibek Omarov <a1ba.omarov at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |a1ba.omarov at gmail dot com

--- Comment #7 from Alibek Omarov <a1ba.omarov at gmail dot com> ---
Can confirm, it still happens with GCC/libstdc++ 13.0. However, in my case,
it's in static initializer.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast
       [not found] <bug-82366-4@http.gcc.gnu.org/bugzilla/>
  2023-10-27  4:13 ` [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast a1ba.omarov at gmail dot com
@ 2023-10-27  6:41 ` redi at gcc dot gnu.org
  2023-10-27  6:46 ` redi at gcc dot gnu.org
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2023-10-27  6:41 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
We still don't have a complete description of the problem though.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast
       [not found] <bug-82366-4@http.gcc.gnu.org/bugzilla/>
  2023-10-27  4:13 ` [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast a1ba.omarov at gmail dot com
  2023-10-27  6:41 ` redi at gcc dot gnu.org
@ 2023-10-27  6:46 ` redi at gcc dot gnu.org
  2023-10-27  6:53 ` redi at gcc dot gnu.org
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2023-10-27  6:46 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
If this only happens when the shared library is loaded from a closed source
application, you really need to talk to Oracle.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast
       [not found] <bug-82366-4@http.gcc.gnu.org/bugzilla/>
                   ` (2 preceding siblings ...)
  2023-10-27  6:46 ` redi at gcc dot gnu.org
@ 2023-10-27  6:53 ` redi at gcc dot gnu.org
  2023-10-27  8:32 ` a1ba.omarov at gmail dot com
  2023-10-27 11:32 ` redi at gcc dot gnu.org
  5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2023-10-27  6:53 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
My best guess for what's happening in the original report is that the shared
library is being loaded into a running process which uses an older version of
libstdc++, and so the locale facets needed by the shared library were never
created at startup. When std::regex tried to use those facets, it fails to find
it.

But without a way to reproduce the problem, this will never get resolved.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast
       [not found] <bug-82366-4@http.gcc.gnu.org/bugzilla/>
                   ` (3 preceding siblings ...)
  2023-10-27  6:53 ` redi at gcc dot gnu.org
@ 2023-10-27  8:32 ` a1ba.omarov at gmail dot com
  2023-10-27 11:32 ` redi at gcc dot gnu.org
  5 siblings, 0 replies; 6+ messages in thread
From: a1ba.omarov at gmail dot com @ 2023-10-27  8:32 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #11 from Alibek Omarov <a1ba.omarov at gmail dot com> ---
I reproduced it with the game engine loading game mod, on Ubuntu Linux system.
Both the engine and the mod are open source, but I'm trying to craft a smaller
example.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast
       [not found] <bug-82366-4@http.gcc.gnu.org/bugzilla/>
                   ` (4 preceding siblings ...)
  2023-10-27  8:32 ` a1ba.omarov at gmail dot com
@ 2023-10-27 11:32 ` redi at gcc dot gnu.org
  5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2023-10-27 11:32 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Is the engine a C++ application, or C, or something else?

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-10-27 11:32 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-82366-4@http.gcc.gnu.org/bugzilla/>
2023-10-27  4:13 ` [Bug libstdc++/82366] std::regex constructor called from shared library throws std::bad_cast a1ba.omarov at gmail dot com
2023-10-27  6:41 ` redi at gcc dot gnu.org
2023-10-27  6:46 ` redi at gcc dot gnu.org
2023-10-27  6:53 ` redi at gcc dot gnu.org
2023-10-27  8:32 ` a1ba.omarov at gmail dot com
2023-10-27 11:32 ` 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).