* Jasper Spit ([EMAIL PROTECTED]) wrote: > Hi, > > I have developed some c++ wrapper classes around openssl. Now I need to > be able to throw exceptions from within the different openssl callbacks > like e.g. the password & verification callback. This is not a problem on > windows, but it is when using a gcc platform like e.g. linux. For this > to work on these platforms I understand I have to compile openssl with > the -fexceptions flag, to avoid that my application will SIGABRT because > my exception being thrown is 'unexpected'. For this to work, I figured > out I also have to remove the omit-frame-pointer flag when building > openssl, otherwise my application will crash. My question is : is this > flag used for optimilization only or can I expect runtime problems when > not using this flag ? The gcc manpage also says that using this flag > will make debugging impossible on some platforms. Is this the case ?
More or less, yes. -fomit-frame-pointer allows gcc to do more creative things when optimising and this hurts nothing really except, as you noted, debugging. There should be very few optional gcc flags that *don't* work with openssl - if they break anything, it indicates a bug in the code or a bug in gcc. A variety of -W*** warning flags probably won't work if you also specify -Werror because the headers may not be up to pedantic standards, however that's about it really. In other words, you should be ok. If you're in any doubt, please do the following; # ./config -f<...> -W<...> [etc - whatever flags you want] # make # make tests If you want to see the consequences of your actions in terms of performance of, for example, RSA, then run some before-and-after benchmarks using; # ./apps/openssl speed <whatever... use -? to see your options> Cheers, Geoff -- Geoff Thorpe [EMAIL PROTECTED] http://www.openssl.org/ ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
