为什么boost :: interprocess :: managed_shared_memory在构造时会抛出boost :: interprocess_exception? [英] Why does boost::interprocess::managed_shared_memory throw a boost::interprocess_exception upon construction?

查看:94
本文介绍了为什么boost :: interprocess :: managed_shared_memory在构造时会抛出boost :: interprocess_exception?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在下面的代码中,我正在尝试初始化managed_shared_memory对象.调用构造函数时,我看到以下错误消息-

In the code below, I'm trying to initialize a managed_shared_memory object. When the constructor is invoked I see the below error message -

terminatewhat():boost :: interprocess_exception :: library_error中止

为什么会引发此异常?我在ubuntu 16.04 linux操作系统上运行此程序,使用g ++ 9.3.0编译了程序.Boost版本1.58.0

why is this exception being thrown? I'm running this on an ubuntu 16.04 linux OS, compiled the program using g++ 9.3.0. Boost version 1.58.0

struct test_obj {
    size_t x;
    size_t y;
    uint8_t buf[32];
    bool is_valid;
};

class shm_wrapper {
        public:
            shm_wrapper() : m_shm(
                                boost::interprocess::open_or_create, 
                                "my_shm",
                                sizeof(test_obj) )
            {};
        private:
        boost::interprocess::managed_shared_memory m_shm;
};

推荐答案

它中止,因为段管理器控制块的大小不足.

It aborts because the size is insufficient for the segment manager control blocks.

sizeof(test_obj)仅为56个字节(在我的系统上).

sizeof(test_obj) is just 56 bytes (on my system).

如果给段10 KiB,它将报告有效使用的224个字节:

If you give the segment 10 KiB, it reports 224 bytes effectively used:

在Coliru上直播

Live On Coliru

#include <boost/interprocess/managed_mapped_file.hpp>
#include <boost/interprocess/managed_shared_memory.hpp>

namespace bip = boost::interprocess;

#ifdef COLIRU
    using segment_type = bip::managed_mapped_file;
#else
    using segment_type = bip::managed_shared_memory;
#endif

static constexpr size_t SegmentSize = 10 * 1024;

struct test_obj {
    size_t x;
    size_t y;
    uint8_t buf[32];
    bool is_valid;
};

class shm_wrapper {
  public:
    shm_wrapper() : m_shm(bip::open_or_create, "my_shm", SegmentSize){};

    size_t free() const { return m_shm.get_free_memory(); }

  private:
    segment_type m_shm;
};

#include <iostream>
int main() {
    std::cout << sizeof(test_obj) << std::endl;
    shm_wrapper w;
    std::cout << w.free() << "\n";
    std::cout << "Effectively used:" << (SegmentSize - w.free()) << "\n";
}

打印

56
10016
Effectively used:224

摘要

也许您不想要具有动态分配功能的部门经理.在这种情况下,请查看 <代码> shared_memory_object .

要存储哑对象",请执行以下操作:在固定大小的区域中,您不需要细分受众群管理器.您将在 shared_memory_object (或 file_mapping )上使用 mapped_region .

To store a "dumb object" in a fixed-size region, you don't need a segment manager. You'd use a mapped_region on a shared_memory_object (or a file_mapping).

这里是另一个示例 在Coliru上直播

#include <boost/interprocess/shared_memory_object.hpp>
#include <boost/interprocess/file_mapping.hpp>
#include <boost/interprocess/mapped_region.hpp>
#include <iostream>
namespace bip = boost::interprocess;

struct test_obj {
    size_t x;
    size_t y;
    uint8_t buf[32];
    bool is_valid;
};

#ifdef COLIRU
    #include <fstream>
    using mapping_type = bip::file_mapping;
#else
    using mapping_type = bip::shared_memory_object;
#endif

template <typename T>
class shm_wrapper {
    static_assert(std::is_trivial_v<T>);
    static_assert(std::is_standard_layout_v<T>);

#ifdef COLIRU // file mappings require more work to cater for the storage
    struct backing_t { } backing;
    backing_t ensure_file(std::string name, size_t size) {
        std::filebuf fbuf;
        fbuf.open(name, std::ios::in | std::ios::out | std::ios::app | std::ios::binary);
        //set the size, sparsely
        fbuf.pubseekoff(size-1, std::ios_base::beg);
        fbuf.sputc(0);
        fbuf.close();
        return {};
    }
  public:
    shm_wrapper()
        : backing { ensure_file("my_shm", sizeof(T)) },
          m_mappable("my_shm", bip::read_write),
          m_reg(m_mappable, bip::read_write, 0, sizeof(T))
    { }
#else
  public:
    shm_wrapper()
        : m_mappable(bip::open_or_create, "my_shm", bip::read_write),
          m_reg(m_mappable, bip::read_write, 0, sizeof(T))
    {
        m_mappable.truncate(sizeof(T));
    }
#endif

    T& get()             { return *static_cast<T*>(m_reg.get_address()); }
    T const& get() const { return *static_cast<T const*>(m_reg.get_address()); }

    auto size() const { return m_reg.get_size(); } 
    auto flush()      { return m_reg.flush();    } 

  private:
    mapping_type m_mappable;
    bip::mapped_region m_reg;
};

int main() {
    shm_wrapper<test_obj> w;
    std::cout << "x:" << w.get().x << "\n";
    w.get().x ^= 0xa7;
    return w.flush()? 0 : 1;
}

连续运行4倍时打印:

x:0
x:167
x:0
x:167

这篇关于为什么boost :: interprocess :: managed_shared_memory在构造时会抛出boost :: interprocess_exception?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆