Languages

Menu
Sites
Language
Coverage options and to build fails
Hi All,
 
I am making the app with Tizen SDK2.2.
To obtain coverage, gcov configure, build, the emulator following error occurred.
(Coverage options: Properties > Tizen Setting > Code Coverage )
 
"debug_launchpad_preloading_preinitializing_daemon has closed unexpectedly"
 
Sdb log also had logs the following output. 
 
"E/Tizen::App( 2622): static int Tizen::App::_AppLifecycleManager::LaunchCallback(int, void*)(928) > Cannot acquire app for 3901."
 
How to solve?
 
 
 
PS.

This problem did not occur in the Tizen2.1.

 

Edited by: Brock Boland on 17 Mar, 2014 Reason: Paragraph tags added automatically from tizen_format_fix module.
List

Responses

6 Replies
john Smith
Hi, When you are selecting gcov feature at that time, after succefully building of application, you can able to get gcov testing tab in left side of SDK. Are you able to get it? Regarding above error "cann't acquire app", there are many reason for getting that error. I know one reason, If your application .exe file and in manifest file if the application name are different at that time while you are trying to launch application you can get that error. Example, suppose your application .exe file is like basic_app.exe and in manifest file application name is basic, at that time you are going to encounter that error.
masashi itagaki
Hi Smith, The first thing,I very thanks you answered my question. > you can able to get gcov testing tab in left side of SDK.Are you able to get it? No,I'm not. (Incidentally, When a coverage option is attached and built in the sample project of Tizen ,I can able to get gcov testing tab in left side of SDK. Therefore, I believe if there is any problem with my project.) > If your application .exe file and in manifest file if the application name are different at that time while you are trying to launch application you can get that error. Unfortunately, the name of application .exe file and manifest file was the same. Could you tell me if there is a case to be considered for? I've found that: where I also conduct additional. 1.If you build by removing the coverage option, the application was working properly on the emulator. 2.It does not start "gcov" in SDB command has been granted. Example： [Launching the application...] OK: C:\tizen-sdk\tools\sdb.exe -s emulator-26100 launch -p mss -e appname -m run -t NG: C:\tizen-sdk\tools\sdb.exe -s emulator-26100 launch -p mss -e appname -m run -t gcov If NG, error of "Cannot acquire app for " is output.
wil smith
Try deleting the run configurations for your application(Menu Bar -> Run -> Run Configurations... -> Tizen Native Application ), and then rerun your app.
masashi itagaki
Hi wil smith, Thanks for the advice. I try again to remove the run configurations as you say. However, the same problem occurs again unfortunately.
wil smith
Issue seems to be around your project settings. Create a new project, with the same name and copy you source/resource files to it. Then retry...
masashi itagaki
Sorry reply away late. Then, as a result of contact Samsung we will continue to research, I discovered it was a bug. Bug fix is likely to be included in the next release version. I appreciate that you have me going out to my question.Thanks everyone.