Jump to content

Source Error Compiling


Recommended Posts

2 minutes ago, ds_aim said:

seckbloc.h

 

delete CheckSize

Try this. Also, if you plan to remove everything when you get any error from the compiler, you must remove the programming world.

	static void CheckSize(size_t n)
	{
		if (n > ~size_t(0) / sizeof(T))
			throw InvalidArgument("AllocatorBase: requested size would cause integer overflow");
	}

 

Kind Regards ~ Ken

  • Love 1

Do not be sorry, be better.

Link to comment
Share on other sites

Just now, Ken said:

Try this.


	static void CheckSize(size_t n)
	{
		if (n > ~size_t(0) / sizeof(T))
			throw InvalidArgument("AllocatorBase: requested size would cause integer overflow");
	}

 

Kind Regards ~ Ken

Or? Use cryptopp 5.6.3

fixed CVE-2015-2141
cleared most Undefined Behavior Sanitizer (UBsan) findings
cleared all Address Sanitizer (Asan) findings
cleared all Valgrind findings
cleared all Coverity findings
cleared all Enterprise Analysis (/analyze) findings
cleared most GCC warnings with -Wall
cleared most Clang warnings with -Wall
cleared most MSVC warnings with /W4
added -fPIC for 64-bit builds (off for 32-bit builds)
added HKDF class from RFC 5869
switched to member_ptr due to C++ 11 warnings for auto_ptr
initialization of C++ static objects, off by default
GCC and init_priotirty/constructor attributes
MSVC and init_seg(lib)
CRYPTOPP_INIT_PRIORITY disabled by default, but available
improved OS X support
improved GNUmakefile support for Testing and QA
added self tests for additional Testing and QA
added cryptest.sh for systematic Testing and QA
added GNU Gold linker support
added Visual Studio 2010 solution and project files in vs2010.zip
added Clang integrated assembler support
unconditionally define CRYPTOPP_NO_UNALIGNED_DATA_ACCESS for Makefile target 'ubsan' and at -O3
workaround ARMEL/GCC 5.2 bug and failed self test
fixed crash in MQV due to GCC 4.9+ and inlining
fixed hang in SHA due to GCC 4.9+ and inlining
fixed missing rdtables::Te under VS with ALIGNED_DATA_ACCESS
fixed S/390 and big endian feature detection
fixed S/390 and int128_t/uint128_t detection
fixed X32 (ILP32) feature detection
removed _CRT_SECURE_NO_DEPRECATE for Microsoft platforms
utilized bound checking interfaces from ISO/IEC TR 24772 when available
improved ARM, ARM64, MIPS, MIPS64, S/390 and X32 (ILP32) support
introduced CRYPTOPP_MAINTAIN_BACKWARDS_COMPATIBILITY_562
added additional Doxygen-based documentation
ported to MSVC 2015, Xcode 7.2, GCC 5.2, Clang 3.7, Intel C++ 16.00

 

 

5.6.3 already fixed that error/

 

Or just delete CheckSize variable

  • Love 1
Link to comment
Share on other sites

10 minutes ago, ds_aim said:

Or? Use cryptopp 5.6.3

1

Maybe you just need to make a compare between the old version and the newest version. I'm using the last version for my project too. However, don't think yourself like everyone. As I said, if you continue to remove everything when you get any error from the compiler, you must remove the programming world.

Best Regards

Ken

  • Love 2

Do not be sorry, be better.

Link to comment
Share on other sites

  • 3 years later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



  • Similar Content

  • Activity

    1. 0

      Metin2 effect script files (MSE and MSA file) how can convert

    2. 10

      Multi Language System

    3. 0

      We are looking for a C++ and Python programmer

    4. 0

      [Quest Scheduler Request] Is there a way to make a quest run independet of player events? Lets say start quest automatically at server startup?

    5. 111

      Ulthar SF V2 (TMP4 Base)

    6. 0

      Quest function when 102.kill definition whereabouts help

    7. 5

      [M2 FILTER] Customized Client Filter

  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.