cv :: remap segfaults与std :: thread [英] cv::remap segfaults with std::thread

查看：63 发布时间：2020/5/13 23:33:24 c++ multithreading opencv segmentation-fault

本文介绍了cv :: remap segfaults与std :: thread的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我通过以下简单代码获取段错误:

I am getting segfault with the following simple code:

#include "opencv2/highgui/highgui.hpp"
#include "opencv2/imgproc/imgproc.hpp"

#include <iostream>
#include <thread>
#include <unistd.h>

void run() {
    sleep(1);  // see below
    cv::Mat source(10, 10, CV_32FC1, -1);

    cv::Mat result(10, 10, CV_32FC1);
    cv::Mat trX(result.rows, result.cols, CV_32FC1, 5);
    cv::Mat trY(result.rows, result.cols, CV_32FC1, 5);

    cv::remap(source, result, trX, trY, cv::INTER_LINEAR, cv::BORDER_TRANSPARENT);
    std::cout << "done" << std::endl;
}

int main(int argc, char* argv[]) {
    std::thread t1(run);
    t1.join();
    std::thread t2(run);
    t2.join();
    return 0;
}

如果我直接从main()调用两次run()，而完全不使用线程，那么它将很好地工作.如果我交换t1.join();和std::thread t2(run);(也就是说，在第一个线程完成之前启动第二个线程；这是sleep变得很重要的地方)，它也运行良好.

If I call run() twice directly from main(), without using threads at all, it works well. If I swap t1.join(); and std::thread t2(run); (that is, start the second thread before the first finishes; this is where sleep becomes important), it also runs well.

此外，如果我将main更改为

int main(int argc, char* argv[]) {
    std::thread t1(run);
    std::thread t2(run);
    t1.join();
    t2.join();
    std::thread t3(run);
    t3.join();
    return 0;
}

它在第三个线程中发生段故障，但(奇怪的是)并非总是如此:大约成功进行了2-3次传球.但是，我无法在上面有两个线程的情况下成功运行该程序.

it segfaults in the third thread, but (strangely) not always: roughly one run of 2-3 passes successfully. However, I was not able to get a successfull run for the program with two threads above.

source，trX和trY中的特定值似乎并不重要.

It seems that particular values in source, trX and trY are not important.

我正在处理的大型程序在12月正常运行，此后我没有时间进行处理，但是已对系统进行了多次更新.现在，大程序由于完全相同的段错误而失败，因此我认为应该与opencv和/或g ++和/或libstdc ++的较新版本有关.

The big program that I was working on was running properly in December, after which I did not have time to work on it, but have updated the system several times. Now the big program fails with exactly the same segfault, so I think it should be something with newer versions of opencv and/or g++ and/or libstdc++.

我的系统或代码有问题吗?还是一些已知的问题?还是我应该在哪里更好地报告?

Is it some problem with my system or my code? Or is it some known problem? Or where should I better report it?

我正在使用g ++ 6.2.0运行最新的Ubuntu 16.10(我也尝试过4.9，结果相同).可能感兴趣的软件包的特定版本是:

I'm running up-to-date Ubuntu 16.10, with g++ 6.2.0 (I've also tried 4.9 with the same result). The specific versions of packages that may be of interest are:

$ dpkg-query -W -f='${binary:Package}\t${Version}\n' | grep -E '(g\+\+|c\+\+|opencv)'
g++     4:6.1.1-1ubuntu2
g++-4.9 4.9.4-2ubuntu1
g++-5   5.4.1-2ubuntu2
g++-6   6.2.0-5ubuntu12
lib32stdc++6    6.2.0-5ubuntu12
libflac++6v5:amd64      1.3.1-4
libopencv-calib3d2.4v5:amd64    2.4.9.1+dfsg-2.1
libopencv-contrib2.4v5:amd64    2.4.9.1+dfsg-2.1
libopencv-core-dev:amd64        2.4.9.1+dfsg-2.1
libopencv-core2.4v5:amd64       2.4.9.1+dfsg-2.1
libopencv-features2d2.4v5:amd64 2.4.9.1+dfsg-2.1
libopencv-flann2.4v5:amd64      2.4.9.1+dfsg-2.1
libopencv-highgui-dev:amd64     2.4.9.1+dfsg-2.1
libopencv-highgui2.4-deb0:amd64 2.4.9.1+dfsg-2.1
libopencv-imgproc-dev:amd64     2.4.9.1+dfsg-2.1
libopencv-imgproc2.4v5:amd64    2.4.9.1+dfsg-2.1
libopencv-legacy2.4v5:amd64     2.4.9.1+dfsg-2.1
libopencv-ml2.4v5:amd64 2.4.9.1+dfsg-2.1
libopencv-objdetect2.4v5:amd64  2.4.9.1+dfsg-2.1
libopencv-video2.4v5:amd64      2.4.9.1+dfsg-2.1
libsigc++-2.0-0v5:amd64 2.8.0-2
libstdc++-4.9-dev:amd64 4.9.4-2ubuntu1
libstdc++-5-dev:amd64   5.4.1-2ubuntu2
libstdc++-6-dev:amd64   6.2.0-5ubuntu12
libstdc++6:amd64        6.2.0-5ubuntu12
libstdc++6:i386 6.2.0-5ubuntu12

我使用以下命令来构建代码:

I use the following command to build the code:

g++ --std=c++14 test.cpp -lpthread -lopencv_highgui -lopencv_core -lopencv_imgproc -o test

Valgrind输出:

Valgrind outputs:

==18499== Thread 2:
==18499== Invalid read of size 8
==18499==    at 0x690F0BA: ??? (in /usr/lib/x86_64-linux-gnu/libtbb.so.2)
==18499==    by 0x690F18A: ??? (in /usr/lib/x86_64-linux-gnu/libtbb.so.2)
==18499==    by 0x6910CE7: ??? (in /usr/lib/x86_64-linux-gnu/libtbb.so.2)
==18499==    by 0x690F691: ??? (in /usr/lib/x86_64-linux-gnu/libtbb.so.2)
==18499==    by 0x690A01F: ??? (in /usr/lib/x86_64-linux-gnu/libtbb.so.2)
==18499==    by 0x6908164: tbb::internal::allocate_root_with_context_proxy::allocate(unsigned long) const (in /usr/lib/x86_64-linux-gnu/libtbb.so.2)
==18499==    by 0x51D9E21: cv::parallel_for_(cv::Range const&, cv::ParallelLoopBody const&, double) (in /usr/lib/x86_64-linux-gnu/libopencv_core.so.2.4.9)
==18499==    by 0x55AE8A1: cv::remap(cv::_InputArray const&, cv::_OutputArray const&, cv::_InputArray const&, cv::_InputArray const&, int, int, cv::Scalar_<double> const&) (in /usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.2.4.9)
==18499==    by 0x1094AC: run() (in /home/petr/osm/draw/test/test)
==18499==    by 0x10A360: void std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) (in /home/petr/osm/draw/test/test)
==18499==    by 0x10A2ED: std::_Bind_simple<void (*())()>::operator()() (in /home/petr/osm/draw/test/test)
==18499==    by 0x10A2BD: std::thread::_State_impl<std::_Bind_simple<void (*())()> >::_M_run() (in /home/petr/osm/draw/test/test)
==18499==  Address 0xfffffffffffffff7 is not stack'd, malloc'd or (recently) free'd

cv :: remap segfaults与std :: thread [英] cv::remap segfaults with std::thread

问题描述

推荐答案

相关文章

C/C++开发最新文章

热门教程

热门工具

登录关闭

cv :: remap segfaults与std :: thread [英] cv::remap segfaults with std::thread

问题描述

推荐答案

相关文章

C/C++开发最新文章

热门教程

热门工具

登录 关闭

登录关闭