On Sunday, December 2, 2018 at 1:36:08 PM UTC-5, Jeffrey Walton wrote: > > > We are seeing a bad interaction on OS X that's causing a > SIGILL/EXC_BAD_INSTRUCTION. Also see > https://github.com/weidai11/cryptopp/issues/751 . > ... > > We are evaluating potential solutions. If you have some feedback then > please provide it at https://github.com/weidai11/cryptopp/issues/751. >
I checked-in a change on my testing fork at https://github.com/noloader/cryptopp/commit/a2524958e5c4 . It uses an enum for the channel identifier instead of an arbitrary string. The change remediates the problems with strings and non-trivial global objects go away, like extra objects in translation units, static initialization order fiasco and ODR violations. On the downside, if you were using a string like "192.168.1.4:4951" to identify a connection, then the library no long handles the mapping. You now have to manage the mapping in your program.It is easy enough to do with a std::map<std::string, int> . Please provide feedback if you have some. Jeff -- You received this message because you are subscribed to "Crypto++ Users". More information about Crypto++ and this group is available at http://www.cryptopp.com and http://groups.google.com/forum/#!forum/cryptopp-users. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
