Re: NSHashTable with weak objects crashing

2019-07-29 Thread Jordan Schidlowsky
worth a shot, but for whatever reason, we seem to experience heap-use-after-free segfaults when using weak references under ARC in the current libobjc2 runtime. I replace the following functions with their reference implementations below, and it seems to solve our seg-fault issues using weak

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

2019-07-29 Thread Jordan Schidlowsky
A. Awesome. Thanks kindly for posting this. This helps. -Jordan > On Jul 29, 2019, at 5:19 AM, Frederik Seiffert > wrote: > > A quick semi-related update on this in case this useful to someone: in order > to get Android Studio to locate debug information and resolve the >

NSHashTable with weak objects crashing

2019-07-29 Thread Frederik Seiffert
Hi, I’m trying to use an NSHashTable with weak objects (-weakObjectsHashTable) on Android, but it’s segfaulting in addObject: on all architectures (ARM/x86). Does anyone know if this should be supported or what might be going on here? Following is the backtrace: frame #5: 0xca4e2b12

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

2019-07-29 Thread Frederik Seiffert
A quick semi-related update on this in case this useful to someone: in order to get Android Studio to locate debug information and resolve the "___lldb_unnamed_symbol" entries I needed to add "-Wl,--build-id=sha1" to the LDFAGS. This is now fixed in our Android toolchain. Frederik > Am