StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Your <code>Data</code> looks like it is probably UTF-16. I made a quick C program that looks kind of like your question description and played around a little in the interactive Python interpreter. I think this might be enough to point you in the right direction for writing your own formatter?</p> <pre><code>int main () { struct String *mystr = AllocateString(); mystr->AllocatorInstance.len = 10; mystr->AllocatorInstance.Data = (void *) malloc (10); memset (mystr->AllocatorInstance.Data, 0, 10); ((char *)mystr->AllocatorInstance.Data)[0] = 'h'; ((char *)mystr->AllocatorInstance.Data)[2] = 'e'; ((char *)mystr->AllocatorInstance.Data)[4] = 'l'; ((char *)mystr->AllocatorInstance.Data)[6] = 'l'; ((char *)mystr->AllocatorInstance.Data)[8] = 'o'; FreeString (mystr); } </code></pre> <p>Using the <code>lldb.frame</code>, <code>lldb.process</code> shortcuts (only valid when doing interactive <code>script</code>), we can read the <code>Data</code> into a python string buffer easily:</p> <pre><code>>>> valobj = lldb.frame.FindVariable("mystr") >>> address = valobj.GetChildMemberWithName('AllocatorInstance').GetChildMemberWithName('Data').GetValueAsUnsigned() >>> size = valobj.GetChildMemberWithName('AllocatorInstance').GetChildMemberWithName('len').GetValueAsUnsigned() >>> print address 4296016096 >>> print size 10 >>> err = lldb.SBError() >>> print err error: <NULL> >>> membuf = lldb.process.ReadMemory (address, size, err) >>> print err success >>> membuf 'h\x00e\x00l\x00l\x00o\x00' </code></pre> <p>From this point you can do any of the usual python array type things - </p> <pre><code>>>> for b in membuf: ... print ord(b) ... 104 0 101 0 108 0 108 0 111 0 </code></pre> <p>I'm not sure how you can tell Python that this is UTF-16 and should be internalized correctly as wide-chars, that's more a Python question than lldb question -- but I think your best bet here is to not use the <code>SBValue</code> methods (because your <code>Data</code> pointer has an uninformative type like <code>void *</code>, like I did in my test program), but to use the <code>SBProcess</code> memory read method.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload