- The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
The result was redirect to Memory debugger. (non-admin closure) LlamaAl (talk) 20:31, 18 February 2013 (UTC)[reply]
- MemCheck (edit | talk | history | protect | delete | links | watch | logs | views) – (View log · Stats)
- (Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)
Uncited mention of how the term is used by multiple people. Half of the article's text lists similar terms. Not encyclopedic nor a dictionary definition. – voidxor (talk | contrib) 09:01, 7 February 2013 (UTC)[reply]
- Note: This debate has been included in the list of Computing-related deletion discussions. • Gene93k (talk) 15:28, 11 February 2013 (UTC)[reply]
- Note: This debate has been included in the list of Software-related deletion discussions. • Gene93k (talk) 15:28, 11 February 2013 (UTC)[reply]
- Relisted to generate a more thorough discussion so a clearer consensus may be reached.
- Please add new comments below this notice. Thanks, LlamaAl (talk) 00:09, 14 February 2013 (UTC)[reply]
- Redirect to Memory debugger. MemCheck is the name for a few different programs that perform memory debugging functions to test software programs. There are already two MemCheck entries and a Valgrind entry in the list of debugging programs at Memory debugger, so the article is a natural target. I recommend redirect instead of deletion because I think MemCheck could be a popular search term for this kind of program. It's unclear whether this article has any content useful to merge into Memory debugger. --Mark viking (talk) 00:47, 14 February 2013 (UTC)[reply]
- That makes good sense to me. But as the nominator, I'm not going to "vote". – voidxor (talk | contrib) 06:08, 14 February 2013 (UTC)[reply]
- Redirect to Memory debugger; Hal Duston's Memory Allocation Checker (see [1]) seems to be the only content from this article worth a one-sentence mention (but not an entire section) inside Memory debugger. Toffanin (talk) 19:58, 18 February 2013 (UTC)[reply]
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.