lldb cannot po string anymore (worked last week)

Latest Xcode 7.3 (7D1002)

Since yesterday I got the same bug as described here:


http://stackoverflow.com/questions/24125539/xcode-lldb-print-statements-fail-nsundomanager

http://www.openradar.me/search?query=15890965



except that it even happens with NSString variables:



po someString

error: instance method 'URLEncodedString' has incompatible result types in different translation units ('void *' vs. 'NSString *')

error: instance method 'URLDecodedString' has incompatible result types in different translation units ('void *' vs. 'NSString *')

note: instance method 'URLEncodedString' also declared here

note: instance method 'URLDecodedString' also declared here

error: 2 errors parsing expression



I found a workaround for local variables (even though this problem is different):

http://lists.apple.com/archives/xcode-users/2014/May/msg00088.html

ctrl-click on variable in local variables list and choose “print description”

Printing description of someString:

ipad


which helps a little but cannot print more complex commands. Last week, it still worked…



Things I tried:

• quit and relaunch Xcode7 and the simulator (they were both running since several days without relaunch)

• Xcode:Product->Clean and (holding the option key) Clean build folder

• Delete ~/Library/Preferences/com.apple.dt.Xcode.plist

• Delete ~//Library/Developer/Xcode/DerivedData/

• Delete ~/Library/Developer/Xcode/iOS DeviceSupport/*


• Install the latest OS X El Capitan Update 10.11.4


but all that didn’t help. Still can neither p nor po strings in the debugger.



I still have an old Xcode 6 on my Mac (renamed and put away before installation of Xcode 7, then put back in /Applications). And that still works, I can enter “po someString” in the debugger and it prints the string into the debug log. But Xcode 7 doesn´t…



Anyone else seeing this?

What else can I delete or reset to make Xcode 7 work again? I am pretty sure that re-installing Xcode 7 will not help, but since I found no other clues yet will probably try that nevertheless...

lldb cannot po string anymore (worked last week)
 
 
Q