Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
New Contributor
Posts: 2
Registered: ‎08-28-2013
My Device: Z10, Q10, DevAlpha A, B & C
My Carrier: Free

Application crash in Device-Release

[ Edited ]

Greetings everyone,

 

I am using the 10.1.2 IDE with 10.1.0. 4828 NDK. After trying in vain solutions said in many post :

  • Try to get logs on the crash 
    • No postmortem debugging (no .core available since  I don't even have a directory in Sandboxes for the application)
    • Nothing in tmp/slogger2 while in release mode (using slog2 API & slog2info -l)
  • I'm not writing anything in the app directories (only reading a json in the assets)
  • Device-release configuration look for AppName.so (got nothing good trying to have instead AppName.so.1.0.0)
  • Tried to comment even in the main.cpp to find a part of the code with memory management problems
  • I created a new project, copied sources/assets and then filled the bar-descriptor and app.pro based on the old ones

By the way, I am using a homemade static library separated from the project (and working perfectly in device-debug).  Here's my App.pro :

 

APP_NAME = ApplicationName

CONFIG += qt warn_on cascades10
LIBS += -lbbsystem -lbbdata -lbbmultimedia -lmmrndclient -lstrm -lasound -lscreen -lbbmsp -lbbcascadesmaps -lQtLocationSubset -lGLESv1_CM -lbb -lbbplatformbbm -lbbdevice -lbbplatform  -lbbpim

BASEDIR =  $$quote($$_PRO_FILE_PWD_)
LIB_src=$$quote($$BASEDIR/../homeMadeLib)

INCLUDEPATH +=  $$quote($$LIB_SRC/src)
HEADERS += $$quote($$LIB_SRC/src/*.hpp)
HEADERS += $$quote($$LIB_SRC/src/*.h) 

include(config.pri)

device {
    CONFIG(debug, debug|release) {
        # Device-Debug custom configuration
        LIBS += -Bstatic -L $$quote($$LIB_SRC/Device-Debug/) -lhomeMadeLib -Bdynamic \
        -DBUILD_DEBUG_MODE
    }


    CONFIG(release, debug|release) {
        # Device-Release custom configuration
        LIBS += -Bstatic -L $$quote($$LIB_SRC/Device-Release/) -lhomeMadeLib -Bdynamic \
        -DQT_NO_WARNING_OUTPUT -DQT_NO_DEBUG_OUTPUT
    }
}

Does anyone have an idea of what I am doing wrong ? 

Thanks in advance for your help.

 

Developer
Posts: 6,152
Registered: ‎07-05-2012
My Device: Playbook, Dev Alpha C, Z10 LE, Z30
My Carrier: Orange

Re: Application crash in Device-Debug

These are always tricky to track down but the only advice you will get here is generic as we can't see your code.

 

Have you considered some of the debugging techniques that replace memory allocation calls with a 'debugging' library call that outputs memory info?


If you've been helped click on Like Button, if you've been saved buy the app. Smiley Happy

Developer of stokLocker, Sympatico and Super Sentences.
New Developer
Posts: 11
Registered: ‎06-09-2011
My Device: -
My Carrier: -

Re: Application crash in Device-Release

Please, add your manifest

Developer
Posts: 6,152
Registered: ‎07-05-2012
My Device: Playbook, Dev Alpha C, Z10 LE, Z30
My Carrier: Orange

Re: Application crash in Device-Release

Similer thread here (with possible solution), might or might not be relevant...

 

http://supportforums.blackberry.com/t5/Native-Development/Release-Build-crashes-on-Startup-Debug-run...


If you've been helped click on Like Button, if you've been saved buy the app. Smiley Happy

Developer of stokLocker, Sympatico and Super Sentences.
New Contributor
Posts: 2
Registered: ‎08-28-2013
My Device: Z10, Q10, DevAlpha A, B & C
My Carrier: Free

Re: Application crash in Device-Release

[ Edited ]

Thanks for your suggestions.

 

Here's my manifest:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!--
  
   Copyright (c) 2011, 2012, 2013 Research In Motion Limited.
  
   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at
  
   http://www.apache.org/licenses/LICENSE-2.0
  
   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
  
-->
<qnx xmlns="http://www.qnx.com/schemas/application/1.0">

<!-- BlackBerry 10 application descriptor file.

    Specifies parameters for identifying, installing, and launching native applications on BlackBerry 10.

-->

    <!-- A universally unique application identifier. Must be unique across all BlackBerry 10 applications.
         Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
    <id>fr.appName.com</id>

    <!-- The name that is displayed in the BlackBerry 10 application installer. 
         May have multiple values for each language. See samples or xsd schema file. Optional. -->
    <name>AppName</name>
    
    <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade. 
         Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
         An updated version of application must have a versionNumber value higher than the previous version. Required. -->
    <versionNumber>1.0.0</versionNumber>

    <!-- Fourth digit segment of the package version. First three segments are taken from the 
         <versionNumber> element.  Must be an integer from 0 to 2^16-1 -->
    <buildId>13</buildId>
                 
    <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
    <!-- <versionLabel></versionLabel> -->

    <!-- Description, displayed in the BlackBerry 10 application installer.
         May have multiple values for each language. See samples or xsd schema file. Optional. -->
    <description>The AppName application</description>

    <!-- Copyright information. Optional. -->
    <!-- <copyright></copyright> -->

    <!--  Name of author which is used for signing. Must match the developer name of your development certificate. -->
    <author>Company</author>
    <category>core.media</category>
    <icon>
       <image>icon-app.png</image>
    </icon>
    <configuration name="Device-Debug">
       <platformArchitecture>armle-v7</platformArchitecture>
       <asset path="arm/o.le-v7-g/AppName" entry="true" type="Qnx/Elf">AppName</asset>
    </configuration>
    <configuration name="Device-Release">
       <entryPointType>Qnx/Cascades</entryPointType>
       <platformArchitecture>armle-v7</platformArchitecture>
       <asset path="arm/o.le-v7/AppName.so" entry="true" type="Qnx/Elf">AppName.so</asset>
    </configuration>
    <configuration name="Device-Profile">
       <platformArchitecture>armle-v7</platformArchitecture>
       <asset path="arm-p/o.le-v7-g/AppName" entry="true" type="Qnx/Elf">AppName</asset>
    </configuration>
    <configuration name="Simulator-Debug">
       <platformArchitecture>x86</platformArchitecture>
       <asset path="x86/o-g/AppName" entry="true" type="Qnx/Elf">AppName</asset>
    </configuration>
    
    <!--  Unique author ID assigned by signing authority. Required if using debug tokens. -->
    <!-- <authorId>xxxxxxxxxxxxxx</authorId> -->
   
    <initialWindow>
        <autoOrients>true</autoOrients>
        <systemChrome>none</systemChrome>
        <transparent>false</transparent>
    </initialWindow>
    
    <!--  The icon for the application, which should be 114x114. -->

    <asset path="icon.png">icon.png</asset>
    <asset path="assets">assets</asset>
    
    <!-- Locale support -->
    <asset path="translations" dest="qm">
        <include name="*.qm"/>
    </asset>
    <asset path="assets/images/icon-app.png">icon-app.png</asset>
    
    <!-- Request permission to execute native code.  Required for native applications. -->
    <permission system="true">run_native</permission>
    <permission>access_location_services</permission>
    <permission>access_internet</permission>
    <env var="LD_LIBRARY_PATH" value="app/native/lib:/usr/lib/qt4/lib"/>

</qnx>

 

New Developer
Posts: 169
Registered: ‎04-12-2010
My Device: Storm
My Carrier: Verizon

Re: Application crash in Device-Release

Had the very same problem, looked @ my code for memory leaks and stuff nothing I could find... I wrote a file as the very 1st line in main, running on the device created the file, installing the bar it would blow up withouth even showing up the  splash

 

So QML was the suspect checked them out they looked fine, looked at the log messages and I saw I had pickerMode/pickerType/pickerViewmode reference error can't find  message in my main.qml WTF???? ... I commented out the FilePicker from attachedObjects and Voila it fired up , of course the section that uses the FilePicker is not working anymore.

 

Does anybody knows why it'd do that???? I'm recycling the file Picker sample from http://blackberry.github.io/Cascades-Samples/filepicker.html almost to the letter and it works fine but if I put it back  my App blows up

 

Developer
Posts: 6,152
Registered: ‎07-05-2012
My Device: Playbook, Dev Alpha C, Z10 LE, Z30
My Carrier: Orange

Re: Application crash in Device-Release

[ Edited ]

@becker666 although the crash is similer the cause is unlikely to be, to avoid muddying this thread and taking focus away from the OP, can you post your own problem in a seperate thread. Thanks.


If you've been helped click on Like Button, if you've been saved buy the app. Smiley Happy

Developer of stokLocker, Sympatico and Super Sentences.