version 2413 debug and release lib behave differently

asked 2016-12-01 22:16:48 -0500

ytlee gravatar image

updated 2016-12-02 07:11:12 -0500

the imread function in the debug version is not working correctly for windows 7/10..

Testing functionality

#include <opencv2/core/core.hpp>
#include <opencv2/highgui/highgui.hpp>
#include <iostream>

using namespace cv;
using namespace std;

int main(int argc, char** argv)
{
    if (argc != 2)
    {
        cout << " Usage: display_image ImageToLoadAndDisplay" << endl;
        return -1;
    }

    Mat image;
    image = imread(argv[1], CV_LOAD_IMAGE_GRAYSCALE); // Read the file

    if (!image.data) // Check for invalid input
    {
        cout << "Could not open or find the image" << std::endl;
        return -1;
    }
 return 0;
    }

and said Could not open

edit retag flag offensive close merge delete

Comments

whats the differently behaviour? Any Error Codes or sth. similar? Or some code snippet so it is possible to reproduce what you are talking about?

Vintez gravatar imageVintez ( 2016-12-02 01:58:24 -0500 )edit

Have you set your arg values in VC2015? if yes, which value?

Vintez gravatar imageVintez ( 2016-12-02 04:11:31 -0500 )edit

Try absolute paths, your system is unable to find the location of the image. Probably you only have the arguments configured for debug mode and not for release.

StevenPuttemans gravatar imageStevenPuttemans ( 2016-12-02 07:11:57 -0500 )edit

The internal test version was code with absolute value "t:\test\one,jpg". The code I posted in the forum was tested with t:\test\one.jpg set in property>debugging>command arguement. In both cases, the release version worked and the debug version failed. BTW, version 3.0 does not have same issue.

ytlee gravatar imageytlee ( 2016-12-02 11:27:10 -0500 )edit
1

could you try to hardcode the path for testing once? -> cv::Mat image = cv::imread("t:\test\one,jpg", 0);

Vintez gravatar imageVintez ( 2016-12-05 02:04:06 -0500 )edit

property>debugging>command argument Be aware that this only sets the argumen for the debugging configuration. Once you select release on top, you are not using these arguments ...

StevenPuttemans gravatar imageStevenPuttemans ( 2016-12-05 02:54:04 -0500 )edit
1

Yesterday, I received a notice from Bill, the bug has been fixed. I pulled the latest built and confirmed the fix.

ytlee gravatar imageytlee ( 2016-12-05 15:22:06 -0500 )edit