dlopen failed: cannot locate symbol "_ZNK7android9CallStack4dumpEPKc" referenced by "gralloc.omap3.so"
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
I have download the rowboat android 4.3 and porting for DM3730 Based board.
During the android startup/booting ...Facing the problem of symbol not found.
D/libEGL ( 1891): loaded /system/lib/egl/libGLESv2_POWERVR_SGX530_125.so
W/libEGL ( 1891): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
E/HAL ( 1891): load: module=/system/lib/hw/gralloc.omap3.so
E/HAL ( 1891): dlopen failed: cannot locate symbol
"_ZNK7android9CallStack4dumpEPKc" referenced by "gralloc.omap3.so"...
E/SurfaceFlinger( 1891): gralloc module not found
E/SurfaceFlinger( 1891): hwcomposer module not found
E/SurfaceFlinger( 1891): ERROR: failed to open framebuffer (Invalid argument),
aborting
F/libc ( 1891): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread
1892 (SurfaceFlinger)
I/DEBUG ( 1123): *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
***
Please suggest me how can i solve this. Your answers are highly appreciated.
Regards,
Alex
```
Original issue reported on code.google.com by `alexva...@gmail.com` on 1 Aug 2014 at 7:26
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the gralloc.omap3.so loading failure and the missing android::CallStack::dump symbol in the Android 4.3 boot log. Check the gralloc and CallStack build compatibility; done means SurfaceFlinger can load the gralloc module and boot proceeds past the framebuffer error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100