[Lldb-commits] [PATCH] Make SBValue::GetNonSyntheticValue return really that.

[Siva Chandra]

I have a case where in the ValueObject backing the SBValue (via the ValueImpl) is itself a synthetic value. I hoped to get the non-synthetic version by calling SBValue::GetNonSyntheticValue. Before the proposed change, it was only returning the SBValue made from the backing ValueObject (which was synthetic) and hence was in a way returning itself.

Should this case not happen at all? I am hitting this under the following scenario for a type:

1. It has synthetic children (implemented via a Python script)
2. It has a summary (also via a Python script). The summary implementation wants the non-synthetic version (as it wants to call methods like GetChildMemberWithName etc.), but gets the synthetic version because a synthetic children provider is registered.


http://reviews.llvm.org/D10581

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/