Boost C++ Libraries: Ticket #12914: Program using BOOST_LOG_TRIVIAL exits with code 255

attachment set

Sun, 19 Mar 2017 20:30:54 GMT

attachment → main.cpp

The BOOST_LOG_TRIVIAL example

Andrey Semashev — Sun, 19 Mar 2017 23:41:11 GMT

VS2017 is not supported in Boost 1.63. I think, it isn't even possible to compile Boost 1.63 with that compiler. The support is being worked on in 1.64.

Also, the exit code of 255 is just -1, which is likely synthesized by the runtime because of errors like a crash or an uncaught exception. Can you verify if such an error happens? If yes, can you provide a backtrace?

attachment set

Mon, 20 Mar 2017 22:25:40 GMT

attachment → project-config.jam

Mon, 20 Mar 2017 22:27:48 GMT

I got Boost 1.63 to compile with MSVC 14.10 by cloning the development branch of boost build to build the b2.exe executable. I also got Boost 1.63 to compile with MSVC 14.10 by modifying the project-config.jam file (I attached a copy of my project-config.jam).

I don't think the Windows system exit code 255 is -1 since they seem to range from 0 to 159999. Reference: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

I'm not sure how to get a stack trace because the program won't hit any set breakpoints (not even the first line of main). It just tends to crash immediately when I use anything from boost log in my code.

From my understanding, the boost log library is only linked when I call a function or macro from it. If I don't use any code from boost log, the program works as expected. Anytime I use a symbol from boost log, the program immediately exits with code 255. I suspect this is caused by linking the boost log library?

status changed; resolution set

Andrey Semashev — Sat, 25 Mar 2017 17:01:44 GMT

status new → closed
resolution → worksforme

I can't reproduce this with the current develop branch. I've compiled libs/log/example/trivial with this command line:

b2 -j 8 link=static runtime-link=static threading=multi address-model=64

No modifications to Boost.Build, Boost.Log or its dependencies were necessary. I did not modify project-config.jam, its contents are as follows:

import option ;
using msvc ;
option.set keep-going : false ;

The example runs fine and the output is as expected.

I'm using VS 2017 Community edition, cl version is 19.10.25017. I'm on Windows 8.1.

Frankly, I don't know what to suggest to debug the problem. It's probably related to your environment. Maybe VS 2017 installation is broken, or some dll is missing. Try checking that with Dependency Walker.

anonymous — Sat, 25 Mar 2017 17:07:14 GMT

Hi Andy,

I managed to get it working today by upgrading to Boost 1.64. I am also using Cmake for my builds, which I also upgraded to the most recent version. The libraries compiled and ran as expected right out of the box with VS 2017 MSVC-14.10 on Windows 10 :)