0

So, I have been using ReactiveSwift for a long time. Most of the time, when I am using po I am able to see the value of a instance/local/global variable. But there are times when the call stack is so deep, that calling po would fail.

Attached screenshot of said failing scenario. enter image description here

Joshua Francis Roman
  • 889
  • 4
  • 16
  • In this context, lldb isn't able to get the current value for the generic type of self. You can tell that because we write the type of self with τ_0_0, which is a positional marker into the swift metadata, not a realized type. There's not enough info here to tell why this failed. If you are interested in following this up, and have an example of the problem you can make available, please file a bug with http://bugs.swift.org. – Jim Ingham Sep 04 '19 at 17:20
  • If you have a chance you might also try this with Xcode 11 when it comes out. That release fixed a fair number of cases where generic->actual type resolution was failing. – Jim Ingham Sep 04 '19 at 17:22

0 Answers0