StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3464872
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-12T05:01:31.737
FavoriteCount
0
LastActivityDate
2010-08-12T05:01:31.737
LastEditDate
2017-05-23T10:32:43.397
LastEditorUserId
-1
OwnerUserId
149482
ParentId
3464838
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Most of these errors will be picked up by passing the appropriate <a href="https://stackoverflow.com/questions/3375697/useful-gcc-flags-for-c">warning flags</a> to the compiler. However from the original list, points 1, 5, 6, 7, 8 are very much worth checking as a human, some compiler/flag combinations however will pick up on unhandled values, pointers to automatic memory, and off-by-one errors in array indexing etc. You may want to take a look at such things as <a href="http://gcc.gnu.org/wiki/Mudflap_Pointer_Debugging" rel="nofollow noreferrer">mudflap</a>, <a href="http://valgrind.org/" rel="nofollow noreferrer">valgrind</a>, <a href="http://gcc.gnu.org/wiki/Mudflap_Pointer_Debugging" rel="nofollow noreferrer">efence</a> and others to catch runtime cases you're unaware of. You might also try <a href="http://www.splint.org/" rel="nofollow noreferrer">splint</a>, to augment your static analysis. For the unautomated side of things, try statically following the flow of your program for particular cases, especially corner cases, and verify to yourself that it appears to do the right thing. Try writing <a href="http://en.wikipedia.org/wiki/Unit_testing" rel="nofollow noreferrer">unit tests</a>/test scripts. Be sure to use some automated checking as discussed above. If your emphasis is on testing without any test execution, <a href="http://www.splint.org/" rel="nofollow noreferrer">splint</a> might very well be the best place to start. The technique you want to research is called <a href="http://en.wikipedia.org/wiki/Static_code_analysis" rel="nofollow noreferrer">static code analysis</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POfinding errors in a given c code
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USMatt Joiner
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POfinding errors in a given c code
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.