You are really going to make a lldb_private::CompilerType, since that’s what
backs the Type & ultimately the SBTypes. There’s a self-contained example
where we make a CompilerType to represent the pairs in the synthetic child
provider for NSDictionaries in the function GetLLDBNSPairType in
NSD
On Wed, 2022-01-12 at 11:22 -0800, Jim Ingham wrote:
> If we can’t always get our hands on the siginfo type, we will have to cons
> that type up by hand. But we would have had to do that if we were
> implementing this feature in the expression parser anyway, and we already
> hand-make types to
On Wed, 2022-01-12 at 11:22 -0800, Jim Ingham wrote:
>
> > On Jan 12, 2022, at 4:28 AM, Pavel Labath wrote:
> >
> > I kinda like the cleanliness (of the design, not the implementation) of a
> > $siginfo variable, but you're right that implementing it would be tricky (I
> > guess we'd have to w
On Wed, 2022-01-12 at 13:28 +0100, Pavel Labath wrote:
>
> This wouldn't solve the problem of writing to the siginfo struct, but I
> am not sure if this is a use case Michał is actually trying to solve
> right now (?) If it is then, maybe this could be done through a separate
> command, as we c
