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
Developer
Posts: 580
Registered: ‎04-01-2009
My Device: Z10, PlayBook
My Carrier: NA

warning: Corrupted shared library list: 0x0 != 0x8346000

- Created app using 10.0.6

 

- Installed 10.0.9 SDK

 

- When I try to debug in the simulator, the splash screen loads on the simulator, and then the following prints out in the console of the IDE:

 

MsgNak received - resending
Remote target is little-endian
warning: Corrupted shared library list: 0x0 != 0x8346000
warning: Corrupted shared library list: 0x0 != 0x8346000
warning: Corrupted shared library list: 0x0 != 0x8346000
[New pid 230682637 tid 2]
[New pid 230682637 tid 3]
[New pid 230682637 tid 4]
[New pid 230682637 tid 5]
[New pid 230682637 tid 6]
[New pid 230682637 tid 7]
[New pid 230682637 tid 8]
warning: Corrupted shared library list: 0x0 != 0x8346000
warning: Could not load shared library symbols for libHwEGL.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Corrupted shared library list: 0x0 != 0x8346000
warning: Could not load shared library symbols for 3 libraries, e.g. libegl_gallium.so.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
warning: Corrupted shared library list: 0x0 != 0x8346000
warning: Could not load shared library symbols for libHwGLESv2.so.
Do you need "set solib-search-path" or "set sysroot"?
[New pid 230682637 tid 9]
[New pid 230682637 tid 10]
[New pid 230682637 tid 11]
[New pid 230682637 tid 12]
warning: Corrupted shared library list: 0x0 != 0x8346000
warning: Could not load shared library symbols for libqsqlite.so.
Do you need "set solib-search-path" or "set sysroot"?
[New pid 230682637 tid 13]

Developer
Posts: 580
Registered: ‎04-01-2009
My Device: Z10, PlayBook
My Carrier: NA

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

I also get a screen full of errors trying to launch via Device-Debug:

 

MsgNak received - resending
Remote target is little-endian
[New pid 37572806 tid 2]
[New pid 37572806 tid 3]
[New pid 37572806 tid 4]
[New pid 37572806 tid 5]
[New pid 37572806 tid 6]
[New pid 37572806 tid 7]
[New pid 37572806 tid 8]
warning: Could not load shared library symbols for libusc.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libsrv_um.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libpvr2d.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libIMGegl.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for wsegl-screen.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libImgGLESv2.so.
Do you need "set solib-search-path" or "set sysroot"?
[New pid 37572806 tid 9]

Developer
Posts: 580
Registered: ‎04-01-2009
My Device: Z10, PlayBook
My Carrier: NA

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

Evening creating a new example project (LightningCrossfadeQML) and launching Device-Debug results in failure of this sort.

 

Tried unintalling 10.0.6, 10.0.9, and then re-installing 10.0.9, and still get this problem.

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

Hi there,

 

I tested this myself and was able to reproduce all log lines you received except for the following:

warning: Corrupted shared library list: 0x0 != 0x8346000

 

The app still did run as expected though, so the above line could point to the issue. 

 

What happens after the application splash screen is displayed (does the app crash etc)? 

Are you running or debugging? If debugging does the debugger hit a break point when this issue occurs?

Was this install of the NDK installed overtop an existing install?

Garett
@garettBeuk
--
Goodbye everybody!
Developer
Posts: 580
Registered: ‎04-01-2009
My Device: Z10, PlayBook
My Carrier: NA

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

Interesting.

 

Something that I should also have mentioned is that the debugger breaks at what appears to be the first line of the program, and I have to press the continue button.

 

I believe it just hangs there on the splash screen indefinitely. (yes, running the debugger)

 

This install of the NDK was over top of 10.0.6, yes, but as mentioned above I tried uninstalling 10.0.6 after this problem occurred, uninstalling 10.0.9, and then re-installing 10.0.9, but am getting the same behavior.

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

The debugger breaking on the first line is expected, so we can ignore that symptom as a cause of this issue.

 

When you installed again did you first delete the existing directories? I am worried that file remnants from a previous install may have lingered and could be contributing to this issue. Could you try uninstalling, deleting all directories used by the NDK then install to a fresh directory and Run/Debug to see if the issue still occurs?

Garett
@garettBeuk
--
Goodbye everybody!
Developer
Posts: 580
Registered: ‎04-01-2009
My Device: Z10, PlayBook
My Carrier: NA

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

Developer
Posts: 580
Registered: ‎04-01-2009
My Device: Z10, PlayBook
My Carrier: NA

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

Doing as you suggest has it partially working. I re-created my workspace as well, not sure if that helped.

 

I can now launch and debug the crossfade demo.

 

My app still hangs on the spash screen, but what gets written to the console is more promising:

 

MsgNak received - resending
Remote target is little-endian
[New pid 39760062 tid 2]
[New pid 39760062 tid 3]
[New pid 39760062 tid 4]
[New pid 39760062 tid 5]
[New pid 39760062 tid 6]
[New pid 39760062 tid 7]
[New pid 39760062 tid 8]
warning: Could not load shared library symbols for libusc.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libsrv_um.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libpvr2d.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libIMGegl.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for wsegl-screen.so.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for libImgGLESv2.so.
Do you need "set solib-search-path" or "set sysroot"?
[New pid 39760062 tid 9]
[New pid 39760062 tid 10]
[New pid 39760062 tid 11]
[New pid 39760062 tid 12]
[New pid 39760062 tid 13]
warning: Could not load shared library symbols for libqsqlite.so.
Do you need "set solib-search-path" or "set sysroot"?
[New pid 39760062 tid 14]

 

ie. No more messages about things being corrupt.

 

I think I'll try piecing my app together from scratch and see if I can get it back up and running that way.

Developer
Posts: 580
Registered: ‎04-01-2009
My Device: Z10, PlayBook
My Carrier: NA

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

I've noticed a couple of things worth mentioning Garett:

 

1. I had in my main.qml:

 

layout: DockLayout {
topPadding: 30
leftPadding: 30
}

 

... but the topPadding and leftPadding were underlined in red. However, the Project Explorer wasn't showing any indications that any of my files had problems, nor was I being made aware of this when I debugged/ran the project.

 

Further, if I fix that and then click on the QML preview button, I get:

 

Problem loading qml file: 25:43: DockLayoutProperties is not a type

 

There is no red squiggley nor anything in Project Explorer nor anything upon running/debugging the project that was letting me know about that issue.

Highlighted
Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: warning: Corrupted shared library list: 0x0 != 0x8346000

The QML files are only ever attempted to be compiled by the application at run-time, they are loaded into the BAR file simply as QML text files. This is why there is no debug or runtime check until the file attempts to be loaded. 

 

The QML Code and Design Views should spot any potential issues with the QML itself if using all native QML elements. The issue comes as a result of being able to use C++ defined elements within QML, the QML may be correct and still receive underlined syntax errors/warnings because the view does not resolve the C++ references. This means that putting this at a project-wide error would cause issues and stop compilations due to valid QML. So until the C++ referencing is added the QML documents will only report issues local to themselves.

 

The issue should become less of a problem moving forward as we have entered the "API complete" period. This means that there will be no more compatibility changes, so the first time you create a QML file it will continue to work in subsequent releases, saving you the need to open each one and ensure there are no issues.

 

Here is the new way to set padding to controls:

https://developer.blackberry.com/cascades/documentation/dev/upgrading/layoutchanges.html

 

Hopefully the above explanation helps to clarify why the errors are reported the way they are at this time.

Garett
@garettBeuk
--
Goodbye everybody!