File: test_multi_shared_lib.cpp

package info (click to toggle)
boost1.83 1.83.0-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 545,632 kB
  • sloc: cpp: 3,857,086; xml: 125,552; ansic: 34,414; python: 25,887; asm: 5,276; sh: 4,799; ada: 1,681; makefile: 1,629; perl: 1,212; pascal: 1,139; sql: 810; yacc: 478; ruby: 102; lisp: 24; csh: 6
file content (30 lines) | stat: -rw-r--r-- 1,389 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
/////////1/////////2/////////3/////////4/////////5/////////6/////////7/////////8
// test_multi_shared_lib.cpp: test that implementation of extented_type_info
//		works when using multiple shared libraries
//
// This reproduces a crash that occurred when multiple shared libraries were
// using Boost.Serialization built statically. That causes core singletons to be
// instantiated in each shared library separately. Due to some destruction order
// mixup in the context of shared libraries on linux it is possible, that
// singletons accessed in destructors of other singletons are already destructed.
// Accessing them will then lead to a crash or memory corruption.
// For this we need 2 shared libraries, linked against static boost. They need to
// instantiate extended_type_info_typeid with different types, either by serializing
// 2 types (which will do that internally) or by accessing the singletons directly.

// (C) Copyright 2018 Alexander Grund
// Use, modification and distribution is subject to the Boost Software
// License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at
// http://www.boost.org/LICENSE_1_0.txt)

#include <boost/serialization/config.hpp>

// Both shall instantiate different(!) singletons and return true
BOOST_SYMBOL_IMPORT bool f();
BOOST_SYMBOL_IMPORT bool g();

int main(int argc, char**){
  if(f() && g())
  	return 0;
  return 1;
}