Forums - call fcvMemInit() crash

7 posts / 0 new
Last post
call fcvMemInit() crash
854088176
Join Date: 21 Oct 14
Posts: 6
Posted: Mon, 2014-12-22 01:35

In my project , once I called fcvMemInit(), the program would crash. There was no log to show what have happened. The cpu of my device is snapdragon 801,  the system of my device is Android 4.4.4 .

 

 

  • Up0
  • Down0
ronaldk
Join Date: 9 Oct 12
Posts: 30
Posted: Mon, 2014-12-22 10:17

Can you share the "adb logcat" when the crash happened?

  • Up0
  • Down0
854088176
Join Date: 21 Oct 14
Posts: 6
Posted: Mon, 2014-12-22 19:48

F/libc    (11680): Fatal signal 11 (SIGSEGV) at 0x80b058b8 (code=1), thread 11680 (com.oppo.camera)
 

  • Up0
  • Down0
854088176
Join Date: 21 Oct 14
Posts: 6
Posted: Mon, 2014-12-22 19:49

F/libc    (11680): Fatal signal 11 (SIGSEGV) at 0x80b058b8 (code=1), thread 11680 (com.oppo.camera)
 

  • Up0
  • Down0
ronaldk
Join Date: 9 Oct 12
Posts: 30
Posted: Tue, 2014-12-23 10:42

Is there any other log that has "fastcv" keyword if you call adb logcat?

You can also share the log using: adb logcat DEBUG:* *:S 

This will get the DEBUG tag log only that usually give the Android stack trace when crash/segmentation fault happens.

When the crash happens, does the phone reset/dead or only the apps exit?

  • Up0
  • Down0
854088176
Join Date: 21 Oct 14
Posts: 6
Posted: Wed, 2014-12-24 03:15

Thank you for your reply!  When the crash happens ,just  the apps exit.

Could you give me your email address? I will send  email to you  attached DEBUG tag log text file .

  • Up0
  • Down0
ronaldk
Join Date: 9 Oct 12
Posts: 30
Posted: Mon, 2015-01-05 10:50

if you are okay, you can share the log in this forum

if you can't share it in the forum, you can use the link below

https://developer.qualcomm.com/contact

  • 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.