Am 20.01.23 23:39 schrieb Bob Friesenhahn <bfrie...@simple.dallas.tx.us>: > > On Fri, 20 Jan 2023, Carsten Grzemba via oi-dev wrote: > > > >If libc.so.1 the only involved C code shared object, would that mean that > >libc has to build with gcc10 and option -fexceptions? > > That would depend on who is calling who. Normally the C/C++ run-time arranges > to call a main() routine which is not part of libc. If a shared library is > involved then shared library initializer functions may be called and I am not > sure what code is responsible for that. If the C++ code has static objects > then the C++ run-time needs to assure that those are constructed before > main() is called. >
in this case GCC/G++ 10 runtime x00007fffade26a30 0x00007fffadfa0234 Yes /usr/lib/64/libexiv2.so.27 0x00007fffad9038b0 0x00007fffada061fa Yes /usr/gcc/10/lib/amd64/libstdc++.so.6 0x00007fffaf3a6820 0x00007fffaf3d2f42 Yes (*) /lib/64/libm.so.2 Yes (*) /lib/64/librt.so.1 0x00007fffaf4381f0 0x00007fffaf4491bc Yes /usr/gcc/10/lib/amd64/libgcc_s.so.1 0x00007fffaf0d96e0 0x00007fffaf188440 Yes (*) /lib/64/libc.so.1 0x00007fffad565c60 0x00007fffad598bae Yes (*) /lib/amd64/ld.so.1 (*): Shared library is missing debugging information. > > > > Regardless, GraphicsMagick has a test in its C++ component (Magick++) because > this failure to catch exceptions used to be a common problem. > > Bob > -- > Bob Friesenhahn > bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ > Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt > > _______________________________________________ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev > -- Carsten Grzemba Tel.: +49 3677 64740 Mobil: +49 171 9749479 Email: carsten.grze...@contac-dt.de contac Datentechnik GmbH
_______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
