Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

alt text

What is R6003, R6009, ^@, ^C, ^A etc?

I don't understand the page.

share|improve this question
Looks like the cat couldn't handle it. – Lance Roberts Jul 12 '10 at 16:01
A simple Google of R6003 and R6009 reveals that they are both runtime errors; one is integer divide by 0, the other is not enough space for environment. I'll leave it up to you to decide which is which. The carat-prefixed symbols are control codes that were converted to ascii text. ^M is a newline, for example. Basically... it's a type of messed up error you might get trying to read a stack trace while doing some old sk00l hacking. – Randolpho Jul 12 '10 at 16:18
@Randolpho: Where do these names (like R6003 etc) come from? – Moeb Jul 12 '10 at 17:44
@Lance: It's still workin on ur problemz. – Andrew Grimm Jul 12 '10 at 23:06
up vote 28 down vote accepted

This is roughly what you'd see when you open an old MS-DOS program (.exe) in a text editor. They scrolled the page until something recognizable showed up. Which are the runtime errors that the Microsoft C-runtime can show when it has to abort the program due to an unrecoverable error. Like stack overflow.

The editor has a bit of trouble with some of the bytes in the file that are control codes in ASCII. Showing them with a ^ followed by a letter that's the code + 0x40, an old convention. So ^@ is 0x00, ^A is 0x01, ^C is 0x03, ^M is 0x0D (carriage return), etcetera. It displays 0x0A as-is, interpreted as a line-feed that terminates the line. Which gives clues to the editor's origin, it is a Unix editor. One way in which Unix and Dos/Windows are famously incompatible, a line-ending in Unix is "\n" but is "\r\n" in Windows. Noted by @badp, the color scheme suggests gedit was used.

Some of the runtime errors are still defined in modern Windows C/C++ programs that were built with Microsoft's C compiler. Like R6018. But not StackOverflow anymore, that's handled by the operating system today. Exception code 0xC00000FD, STATUS_STACK_OVERFLOW. Don't bother sending the error report to Microsoft, they already have a billion of them.

share|improve this answer
Those look like gedit themes. – badp Oct 9 '10 at 13:12

Error codes was defined in cmsgs.h for MS C compiler, for ages ago, talking DOS here.. Not sure if this is the correct reference, but anyhow close.

*cmsgs.h - runtime errors
*       Copyright (c) 1990-1997, Microsoft Corporation. All rights reserved.
*       The file defines, in one place, all error message strings used within
*       the C run-time library.
*       [Internal]

#if _MSC_VER > 1000
#pragma once
#endif  /* _MSC_VER > 1000 */

#ifndef _INC_CMSGS
#define _INC_CMSGS

#ifndef _CRTBLD
 * This is an internal C runtime header file. It is used when building
 * the C runtimes only. It is not to be used as a public header file.
#error ERROR: Use of C runtime library internal header file.
#endif  /* _CRTBLD */

 * runtime error and termination messages

#ifdef _MAC
#define EOL "\n"
#else  /* _MAC */
#define EOL "\r\n"
#endif  /* _MAC */

#define _RT_STACK_TXT      "R6000" EOL "- stack overflow" EOL

#define _RT_FLOAT_TXT      "R6002" EOL "- floating point not loaded" EOL

#define _RT_INTDIV_TXT     "R6003" EOL "- integer divide by 0" EOL

#define _RT_SPACEARG_TXT   "R6008" EOL "- not enough space for arguments" EOL

#define _RT_SPACEENV_TXT   "R6009" EOL "- not enough space for environment" EOL

#define _RT_ABORT_TXT      "" EOL "abnormal program termination" EOL

#define _RT_THREAD_TXT     "R6016" EOL "- not enough space for thread data" EOL

#define _RT_LOCK_TXT       "R6017" EOL "- unexpected multithread lock error" EOL

#define _RT_HEAP_TXT       "R6018" EOL "- unexpected heap error" EOL

#define _RT_OPENCON_TXT    "R6019" EOL "- unable to open console device" EOL

#define _RT_NONCONT_TXT    "R6022" EOL "- non-continuable exception" EOL

#define _RT_INVALDISP_TXT  "R6023" EOL "- invalid exception disposition" EOL

 * _RT_ONEXIT_TXT is specific to Win32 and Dosx32 platforms
#define _RT_ONEXIT_TXT     "R6024" EOL "- not enough space for _onexit/atexit table" EOL

#define _RT_PUREVIRT_TXT   "R6025" EOL "- pure virtual function call" EOL

#define _RT_STDIOINIT_TXT  "R6026" EOL "- not enough space for stdio initialization" EOL

#define _RT_LOWIOINIT_TXT  "R6027" EOL "- not enough space for lowio initialization" EOL

#define _RT_HEAPINIT_TXT   "R6028" EOL "- unable to initialize heap" EOL

 * _RT_DOMAIN_TXT, _RT_SING_TXT and _RT_TLOSS_TXT are used by the floating
 * point library.
#define _RT_DOMAIN_TXT     "DOMAIN error" EOL

#define _RT_SING_TXT       "SING error" EOL

#define _RT_TLOSS_TXT      "TLOSS error" EOL

#define _RT_CRNL_TXT       EOL

#define _RT_BANNER_TXT     "runtime error "

#endif  /* _INC_CMSGS */
share|improve this answer

It reminds me more about the old Apple ][e, when booting, displaying a screen of random characters, with ^@ for zeroes...

share|improve this answer

SO mods are trying too hard to make it look 'geeky'.

share|improve this answer
Yes, for the youngsters here it already looks geeky, for some of us, its flashbacks from the good old days, single user,single tasking, oh my.. – neslekkiM Oct 9 '10 at 12:15
They don't have to try so hard, really. Just say, "We are sorry, SO is down due to ..." – OTZ Oct 9 '10 at 12:21
Actually it's not the SO Mods. We have nothing to do with it. It is really the SO Development Team that comes up with this stuff, and in fact, there is a lot of work and discussion around it. It is what makes SO better then most other sites. But then again, you have to appreciate the site and it's history to understand that. – BinaryMisfit Oct 9 '10 at 12:32
@Diago It would be extremely hard to appreciate the site if one gets suspended for breaking rules that don't exist, can't post questions any longer on meta, receives a follow-up suspension on SO simply because a question was migrated to meta, would it? – OTZ Oct 9 '10 at 12:39
Considering your profile, and the quality of your posts, I am extremely surprised you survived without suspension as long as you did. The rules are clearly defined in the FAQ, and you triggered the automatic banning system for bad quality questions. Honestly, the site has a high standard, and if your not willing to get better, improve and appreciate the site, it's better off not having you around. Also, when you don't even have a email in your profile, it's impossible for any mod to let you know why you got suspended. We do not discuss suspension on MSO, but your profile speak for itself. – BinaryMisfit Oct 9 '10 at 13:09
@Diago Thanks you very much for taking a look. While it is rare to encounter a dia-mod that says "we don't need you here," I definitely love your honesty. So automatic banning system suspended me for a week for having posted bad questions. I'll take your word for it. But you haven't mentioned the reason why I am no longer allowed to post questions on MSO and exactly why I was banned on SO yesterday in addition. Would you mind elaborating on those points please? – OTZ Oct 9 '10 at 19:06
I have no idea. The automatic IP bans will not suspend your account, it will simply prevent you from posting any questions. Your account suspension on SO I cannot track because I am not a mod there, and as already mentioned no mod can contact you to tell you. It's not within my power to investigate. I simply commented on what I can see, and what would trigger my mod senses. I would suggest you read this post with regards to why you can't post questions here. – BinaryMisfit Oct 9 '10 at 19:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .