Open oryonatan opened 2 days ago
Hi @oryonatan, I've not been able to replicate this and I've moved to Xcode 16.1 but I imagine this is related to a long known problem that LLDB is not really written with dynamic loading individual source files in mind as opposed to modules. For example, if you have a view controller, inject and break in it and try to p self
or view instance variables of self. This has never worked when it tries to look up the type. I think this is just a new warning they've added that notices this problem. If it's not causing you problems try to ignore it as there is very little that can be done about it. I looked at the source a long time ago and raised an issue but it is very, very difficult working on LLDB. TBH it's a minor miracle breakpoints in injected code have always been so reliable apart from this!
(lldb) p self
(TestInjection.ViewController) 0x0000000133037c00 <No Swift runtime type info for $s13TestInjection14ViewControllerCD>
P.S. I've seen this message today looking at another issue. Perhaps it is more related to debugging code that wasn't built on your machine. Do you get this problem if you build your own InjectionNext.app binary? B.T.W. I have a branch cursor-mode
open with changes to support "Cursor" better. Can you build off that please ensure I hadn't broken anything in the process?
When running on XCode 16.1 (and probably on 16 also), after injecting a line and setting a breakpoint after the injected line, I get the console spammed with messages of this format,
It is not clear if there is really an issue with the debugger, or these messages can be ignored.
Tested on XCode Version 16.1 (16B40) Mac OS 15.1 (24B83) My Mac (Designed for iPad) run destination.