Results 1 to 2 of 2

Thread: Crash when initializing map, Fatal signal 11 (SIGSEGV) with Android SDK

  1. #1
    Neuer skobbler
    Join Date
    21.01.2016
    Posts
    6

    Crash when initializing map, Fatal signal 11 (SIGSEGV) with Android SDK

    Hello,

    I am using the Android SDK, version 2.5.1 to develop an application. I recently started to encounter a Fatal signal 11 (SIGSEGV) error in which my application closes. Here is the stack trace:

    Code:
    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    01-20 22:31:16.378 304-304/? I/DEBUG: Build fingerprint: 'lge/g3_vzw/g3:5.1.1/LMY47V/1525410464a1b:user/release-keys'
    01-20 22:31:16.378 304-304/? I/DEBUG: Revision: '10'
    01-20 22:31:16.378 304-304/? I/DEBUG: ABI: 'arm'
    01-20 22:31:16.379 304-304/? I/DEBUG: pid: 6320, tid: 6398, name: GLThread 584  >>> com.visornav.app <<<
    01-20 22:31:16.379 304-304/? I/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x44
    01-20 22:31:16.398 304-304/? I/DEBUG:     r0 00000000  r1 b483da00  r2 00000000  r3 00000001
    01-20 22:31:16.399 304-304/? I/DEBUG:     r4 b483e400  r5 a08e9000  r6 00000000  r7 00000000
    01-20 22:31:16.399 304-304/? I/DEBUG:     r8 a09eb480  r9 aebff740  sl 00000011  fp a08e9000
    01-20 22:31:16.399 304-304/? I/DEBUG:     ip 00000000  sp aebff6c0  lr a2977ec9  pc a2977f10  cpsr 200f0030
    01-20 22:31:16.400 304-304/? I/DEBUG:     #00 pc 000ddf10  /data/app/com.visornav.app-1/lib/arm/libngnative.so (TileLoader::load(MapViewInterplay const&, std::vector >&, std::vector >&, std::vector >&)+207)
    01-20 22:31:16.401 304-304/? I/DEBUG:     #01 pc 00120a65  /data/app/com.visornav.app-1/lib/arm/libngnative.so (MapRenderer::doUpdateTiles()+780)
    01-20 22:31:16.401 304-304/? I/DEBUG:     #02 pc 0011f2e9  /data/app/com.visornav.app-1/lib/arm/libngnative.so (MapRenderer::Draw(bool)+472)
    01-20 22:31:16.401 304-304/? I/DEBUG:     #03 pc 0011ecab  /data/app/com.visornav.app-1/lib/arm/libngnative.so (MapRenderer::DrawWrapper(bool)+98)
    01-20 22:31:16.402 304-304/? I/DEBUG:     #04 pc 000ffa8d  /data/app/com.visornav.app-1/lib/arm/libngnative.so (NG_Render+24)
    01-20 22:31:16.402 304-304/? I/DEBUG:     #05 pc 000e8607  /data/app/com.visornav.app-1/lib/arm/libngnative.so (Java_com_skobbler_ngx_map_MapRenderer_render+6)
    01-20 22:31:16.402 304-304/? I/DEBUG:     #06 pc 0017963b  /data/dalvik-cache/arm/data@app@com.visornav.app-1@base.apk@classes.dex
    This happens when I am launching my app, the view is set, and as the tiles are loading the app crashes with this error. This does not happen with the Demo SDK Project. I know the stack trace mentions GLThread but I do not get an onGLInitializationError() call.

    I'm not sure what I can do my end other than to figure out what the demo project did correctly. My application has worked before this happened but it just displayed a map and buttons. I appreciate any advice on this

    EDIT: I fixed my issue! I was calling SKMapsInitSettings.setMapResourcesPaths() wrong, the path I was setting didn't exist due to a typo so it was incorrect. It would be nice if the directory was checked so a java exception could be thrown instead of an error at the native level.
    Last edited by Techknow; 22.01.2016 at 01:09. Reason: Fixed my issue

  2. #2
    Oberskobbler
    Join Date
    22.07.2014
    Posts
    399
    Thanks for updating the thread and mentioning the solution. We'll consider your suggestion for the future improvements.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •