StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17990117
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-01T09:25:53.797
FavoriteCount
0
LastActivityDate
2013-08-01T09:25:53.797
LastEditDate
LastEditorUserId
0
OwnerUserId
2549230
ParentId
17972945
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
After some tests I figured things out, answering for anyone looking for this information : <blockquote> Can someone confirm I am going the right way structuring my Elf file this way ? </blockquote> Yes. As GDB is accepting the file, this seems to be the right way of doing. Results shown by readelf -a show the correct structure, good so far. <blockquote> I am not sure about where should lay the data (note & program sections) into my file : is there a mandatory order, or is this my program headers offset that define where the data is ? </blockquote> Offsets given to <code>Phdr.p_offset</code> should point where the data lays in the Elf file. They start at the very beginning of the file. For example : The p_offset for the <code>PT_NOTE</code> program header should be set at <code>sizeof(ElfW(Ehdr)) + ehdr.e_phnum*sizeof(ElfW(Phdr))</code>. <code>ehdr.e_phnum</code> being the number of program header present in the Elf file. For the <code>PT_LOAD</code> program header, this is a bit longer, cause we will also have to add length of all the note sections. For a "standard" core dump with a note segment containg <code>NT_PRSTATUS</code>, <code>NT_PRPSINFO</code> and <code>NT_AUXV</code> sections, offset for the PT_LOAD data (<code>Phdr.p_offset</code>) will be : <pre><code>sizeof(ElfW(Ehdr)) + ehdr.e_phnum*sizeof(ElfW(Phdr)) + sizeof(ElfW(Nhdr)) + sizeof(name_of_section) + sizeof(struct prstatus) + sizeof(ElfW(Nhdr)) + sizeof(name_of_section) + sizeof(struct prpsinfo) + sizeof(ElfW(Nhdr)) + sizeof(name_of_section) + sizeof(struct auxv_t) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCore dump note section
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USd6bels
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCore dump note section
 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
 VTUndeletion
CommentsPostId
1. This table or related slice is empty.

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.