This forum is disabled, please visit https://forum.opencv.org
 | 1 | initial version |
This is far too less information to make any clues about your problem. I am citing from the OpenCV Wiki on reporting bugs: http://code.opencv.org/projects/OpenCV/wiki/WikiStart (Please don't take this personal):
Reporting bugs
Please, specify your platform (Windows 32/64bit, Linux x86/x64/ppc/..., MacOSX 32/64bit/ppc); compiler version; OpenCV version/revision; whether IPP, OpenMP, MMX, SSE ... have been enabled or not, and any other information that let us reproduce the environment, identify and localize the problem.
A sample code reproducing the problem helps us the most. Please check source://trunk/opencv/samples - for the preferred style (small code size, cross-platform). There is no need to provide any project files or makefiles, if it is a short single-file sample, we could build it and run in a minute.
If your application is complex, and the problem happens somewhere in the middle, often it is still possible to create a short standalone sample: First, capture and store the data that you pass to the function using FileStorage. Then copy the function call and put the corresponding reading from FileStorage in front of it.
If we can reproduce the problem, we can fix it quickly.
| | 2 | No.2 Revision |
This is far too less information to make any clues about your problem. I am citing copy and pasting from the OpenCV Wiki on reporting bugs: bugs. Please supply us with some of the informations, so the problem could be reproduced (http://code.opencv.org/projects/OpenCV/wiki/WikiStart (Please don't take this personal):
Reporting bugs):
Please, specify your platform (Windows 32/64bit, Linux x86/x64/ppc/..., MacOSX 32/64bit/ppc); compiler version; OpenCV version/revision; whether IPP, OpenMP, MMX, SSE ... have been enabled or not, and any other information that let us reproduce the environment, identify and localize the problem.
A sample code reproducing the problem helps us the most. Please check source://trunk/opencv/samples - for the preferred style (small code size, cross-platform). There is no need to provide any project files or makefiles, if it is a short single-file sample, we could build it and run in a minute.
If your application is complex, and the problem happens somewhere in the middle, often it is still possible to create a short standalone sample: First, capture and store the data that you pass to the function using FileStorage. Then copy the function call and put the corresponding reading from FileStorage in front of it.
If we can reproduce the problem, we can fix it quickly.
