StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1001588
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-06-16T13:44:53.113
FavoriteCount
0
LastActivityDate
2009-06-16T15:43:24.420
LastEditDate
2009-06-16T15:43:24.420
LastEditorUserId
123109
OwnerUserId
123109
ParentId
1001448
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
If you're running on Linux, you could run your tests with <a href="http://valgrind.org/docs/manual/quick-start.html#quick-start.mcrun" rel="nofollow noreferrer">memcheck</a>. The <a href="http://valgrind.org/docs/manual/mc-manual.html#mc-manual.clientreqs" rel="nofollow noreferrer">Client Requests</a> section of the manual describes several useful macros, of which one is noted as being useful for testing: <blockquote> <code>VALGRIND_COUNT_LEAKS</code>: fills in the four arguments with the number of bytes of memory found by the previous leak check to be leaked, dubious, reachable and suppressed. Again, useful in test harness code, after calling <code>VALGRIND_DO_LEAK_CHECK</code>. </blockquote> The macro is defined in <code>memcheck.h</code> (likely in <code>/usr/include/valgrind</code>), and the sequence you want will resemble <pre><code>unsigned long base_definite, base_dubious, base_reachable, base_suppressed; VALGRIND_DO_LEAK_CHECK; VALGRIND_COUNT_LEAKS(base_definite, base_dubious, base_reachable, base_suppressed); // maybe assert that they're zero! // call test unsigned long leaked, dubious, reachable, suppressed; VALGRIND_DO_LEAK_CHECK; VALGRIND_COUNT_LEAKS(leaked, dubious, reachable, suppressed); CPPUNIT_ASSERT_EQUAL(base_leaked, leaked); // etc. </code></pre> Repeating that for every test would be a pain, so you might write macros of your own or, even better, a specialized <a href="http://cppunit.sourceforge.net/doc/lastest/class_test_runner.html" rel="nofollow noreferrer">TestRunner</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing CppUnit for memory leak detection
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGreg Bacon
UserOwnerUserId
1. USGreg Bacon
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. 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
 VTUpMod
CommentsPostId
1. COThis does not fail a specific test based on memory leaks...
 singulars
 PostPostId
 PO
 UserUserId
 USJeremy Mayhew
2. COThanks, I should have been clearer. Revised!
 singulars
 PostPostId
 PO
 UserUserId
 USGreg Bacon

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.