[random_device] App crash on boost::ramdom::random_device

Hi there!
My app crash on customer's site. It crashes everytime the app is starting.
It happens on Chinese Windows7 (64bit) OS but it runs well on my PC with Korean Windows7 OS and English Windows7 OS.
My app is built on VisualStudio 2010 (x86 build, C++) using websocketpp library and boost 1.55.
The call-stack from the dump file shows my app(TMSClient100) called websocketpp::endpoint, then it called boost::random::random_device then ThrowException. Here's the call-stack info:
14 001cf6ac 7113872d e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x58
15 001cf6e4 713b7c5a 001cf704 713d9350 b621b77b msvcr100!_CxxThrowException+0x48 [f:\dd\vctools\crt_bld\self_x86\crt\prebuild\eh\throw.cpp @ 157]
16 001cf814 713b7da3 001cf840 b621b9a7 002a19bc TMSClient100!boost::random::random_device::impl::error+0x15a
17 001cf8b8 713b7f7b 001cf8dc b621b94b 00000000 TMSClient100!boost::random::random_device::impl::impl+0x143
18 001cf904 71383901 b621b8ab 001cfac4 002a17e8 TMSClient100!boost::random::random_device::random_device+0x8b
19 001cf928 7137eb2c 002a17e8 b621b8ef 001cfac4 TMSClient100!websocketpp::endpoint

On Fri, 17 Apr 2020 at 16:29, 박형근(HYUNGGUN PARK) via Boost-users < boost-users@lists.boost.org> wrote:
Hi there!
My app crash on customer's site. It crashes everytime the app is starting.
Are you catching the exception? It is permissible for: * random_device not to be available on all systems * random_device's constructor to throw if there was a problem connecting to the (implementation defined) stochastic process. In other words, you cannot rely on it not throwing. If it does, you'll have to fall back to another method of generating random seeds for your pseudo-random generators.
-- Richard Hodges hodges.r@gmail.com office: +442032898513 home: +376841522 mobile: +376380212

On Fri, Apr 17, 2020 at 10:29 AM 박형근(HYUNGGUN PARK) via Boost-users
Check the exception message. Is it failing because it: 1. Could not find a provider name 2. Could not acquire CSP context If #1, this might be solved by upgrading from Boost 1.55 to a newer version. This fix in particular: https://github.com/boostorg/random/commit/dc2fdeac443fb56c87a03a0887c9e7c8e1... went into Boost 1.56. Glen
participants (3)
-
Glen Fernandes
-
Richard Hodges
-
박형근(HYUNGGUN PARK)