-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
enable backtrace in gcc12 #8784
Comments
A new Issue was created by @VinInn Vincenzo Innocente. @smuzaffar, @rappoccio, @Dr15Jones, @antoniovilela, @makortel, @sextonkennedy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
In reality we have to wait for 12.4 to make proper use of it (unless we patch gcc ourselves) |
all issues I reported do GCC (3) have been fixed in all open branches. |
thanks @VinInn , I was hoping that GCC 12.4 will come out soon ( normally gcc does release minor update version in 2nd half of the year). So lets wait a a bit more otherwise we can update to gcc 12 latest in Dec (not that updating gcc does require rebuilding all externals) |
ok. I understand. |
@VinInn , I have managed to build latest gcc 12 branch and managed to build shared library using your example at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936#c1 and successfully ran a tests . Shared library was built to link against
|
#8821 is testing latest GCC 12 for DEVEL IBs |
Would it be possible to enable backtrace in gcc12 adding
--enable-libstdcxx-backtrace=yes
as an option to configure ?
The text was updated successfully, but these errors were encountered: