StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
233424
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-24T12:58:45.007
FavoriteCount
0
LastActivityDate
2008-10-24T12:58:45.007
LastEditDate
LastEditorUserId
0
OwnerUserId
30841
ParentId
232678
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
My first question is how do you calculate len? Is it just strlen or does it include room for the \0 terminator? I think you may be overshooting your allocation in your strcpy. Bad behavior will tend to happen on word boundaries and appear random. Also, check to make sure that your source strings are null terminated. If you made a mistake on the read side and didn't terminate them. Then strcpy may be randomly overwriting things. <pre><code> *(lines + slot) = (char *) malloc(len * sizeof(char)); if(*(lines + slot) == NULL) exit(EXIT_FAILURE); strcpy(*(lines+slot),s); </code></pre> Perhaps try: <pre><code> lines[slot] = (char *) malloc((len + 1) * sizeof(char)); if(lines[slot] == NULL) exit(EXIT_FAILURE); if(strlen(s) <= len){ strcpy(lines[slot],s); } else{ /* do something else... */ } </code></pre> In terms of general form, I'd also encourage you to make a few stylistic changes to make the whole thing a bit more readable, easier to follow and resistant to errors. Pointer arithmetic is valid and fun, but I think your intent is a little more clear if you use the array form like: <pre><code>free(lines[slot]); lines[slot] = NULL; </code></pre> instead of <pre><code>free(*(lines+slot)); *(lines + slot) = NULL; </code></pre> I'd also encourage you to use fewer statics. It's easy enough to through them in a data structure and pass them around into your accessors and mutators. It becomes much more clear where the action is happening prevents you from doing things like: <pre><code>static int numlines = 0; void insert_line(char *s, int len){ int numlines = 5; </code></pre> where you can introduce scoping issues that are just miserable to debug.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMalloc Error: incorrect checksum for freed object
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTodd
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.