Forums - FastCV 1.2.0 crashes

4 posts / 0 new
or Register
Last post
FastCV 1.2.0 crashes
sagiv
Join Date: 2 Sep 12
Posts: 12
Posted: Thu, 2013-02-21 04:41
Top

I'm using the new FastCV 1.2.0 version on my Galaxy Nexus (Android version 4.2.2).

The function fcvGetPerspectiveTransformf32 causes the app to crash with the following message:

 

02-21 14:28:56.176: A/libc(28082): @@@ ABORTING: LIBC: ARGUMENT IS INVALID HEAP ADDRESS IN dlfree addr=0x59003148
02-21 14:28:56.176: A/libc(28082): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 28082 (comm.fastcorner)
 
 
I don't remember this happing in the previous version of FastCV.
 
Is it a bug?
  • Up0
  • Down0
Re: FastCV 1.2.0 crashes
jeff4s Moderator
Join Date: 4 Nov 12
Posts: 106
Posted: Thu, 2013-02-21 11:56
Top

Hi,

Sorry for late reply. We have been working diligently to track down the problem. It turns out there's an elusive bug that causes memory corruption in one of the supporting functions, which explains some inconsistent behavior. Two other APIs are also impacted: fcvSolve32 and fcvFeatureExtract.

We will fix this bug in 1.2.1 release, which is meant to address issues like this. Again we appreciate you reported this issue, and encourage FastCV users or potential users to try out 1.2.0 and report any problems/questions you encounter. We will do our best to support you.

Best regards,

-Jeff

  • Up0
  • Down0
Re: FastCV 1.2.0 crashes
xsalat00
Join Date: 6 Feb 13
Posts: 1
Posted: Thu, 2013-02-28 03:50
Top

Hello,
I have similar problem when I am using fcvGeomPoseEvaluateErrorf32

float projected[64];
float reprojErr[64];
float invz = 0;
float reprojVariance[64];

fcvGeomPoseEvaluateErrorf32(
        &corrs,
        pose,

        projected,
        reprojErr,
        &invz,
        reprojVariance
);

I always get Fatal signal 11 (SIGSEGV) at 0xbec691ac (code=1) and message  "Could not access memory at 0x0"
 

  • Up0
  • Down0
Re: FastCV 1.2.0 crashes
jeff4s Moderator
Join Date: 4 Nov 12
Posts: 106
Posted: Thu, 2013-02-28 09:13
Top

Can you share your test vectors and how you called the function? That will help us investigate the issue.

Thanks,

-Jeff

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.