It's mentioned in the makefile, but if you define NDEBUG in Crypto++ you must also define NDEBUG for your app, and vice versa, because it changes the memory layout of some Crypto++ classes. If you are not doing that consistently, then that's probably what's causing the seg fault.
Is there a reason the GNUMakefile does not build both versions (or have an option too) into separate libs? Also, this was mentioned in a previous post from someone else, why does the release command line not work? If you leave the two options (-ffunction-sections -fdata-sections) in the CXXFLAGS the test suite fails to compile. If you take them out and do "Cryptest z cryptest.exe cryptest.zip" you get an error (forget what now that I am not on linux), but specifying the compression level works? Is the compression level not really optional as the command help suggests?
I have been toying with the compiler settings in GNUMakefile, but so far all attempts to build my app with a release build end with a linker error having a lengthy function name ending in '::assert<number>'. I have a new build running while I am away that may work, but the last two attempts were unsuccessful.
thanks.
michael
