Re: Crash in ___lldb_unnamed_symbol / cannot locate symbol "__start___objc_selectors" on Android

2019-07-01 Thread David Chisnall
Hi, On 01/07/2019 15:38, Frederik Seiffert wrote: Thanks for the explanation David. I believe there was a bug in clang where I didn't add an empty symbol for compilation units that didn't contain any selectors.  If you then linked a program or a library that didn't contain any selectors

Re: Crash in ___lldb_unnamed_symbol / cannot locate symbol "__start___objc_selectors" on Android

2019-07-01 Thread Frederik Seiffert
Thanks for the explanation David. > I believe there was a bug in clang where I didn't add an empty symbol for > compilation units that didn't contain any selectors. If you then linked a > program or a library that didn't contain any selectors then you'd see this > error at link time. This

Re: Crash in ___lldb_unnamed_symbol / cannot locate symbol "__start___objc_selectors" on Android

2019-07-01 Thread David Chisnall
On 01/07/2019 13:14, Frederik Seiffert wrote: 1. When using Qt to build a simple test app with Objective C, I’m getting the following runtime error when launching the app: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__start___objc_selectors" referenced by

Crash in ___lldb_unnamed_symbol / cannot locate symbol "__start___objc_selectors" on Android

2019-07-01 Thread Frederik Seiffert
Hi, I’ve been working on using a more up-to-date Clang with the Android toolchain (in order to use the 2.0 Objective-C runtime), and managed to integrate the Clang r353983 prebuilt into NDK r20. While this seems to work well so far when targeting armeabi-v7a, I am getting the following errors