StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18555372
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-09-01T04:54:04.277
FavoriteCount
0
LastActivityDate
2013-09-01T04:54:04.277
LastEditDate
LastEditorUserId
0
OwnerUserId
1692151
ParentId
18468126
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
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? <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> 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: <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> From this point you can do any of the usual python array type things - <pre><code>>>> for b in membuf: ... print ord(b) ... 104 0 101 0 108 0 108 0 111 0 </code></pre> 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.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPointer arithmetic in LLDB Python scripts
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJason Molenda
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPointer arithmetic in LLDB Python scripts
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COExcellent! `ReadMemory` is exactly what I was looking for - as you said, the concrete data type for the data is uninformative so it makes sense that the `SBValue` methods weren't helpful. Enjoy the well-deserved bounty!
 singulars
 PostPostId
 PO
 UserUserId
 USbenwad

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.