I open up my program with a binary editor and a found about a dozen mesages about bad stuff happening at 0x%08X in the program now my question is where is 0x%08X in the memory stack and how would i find it useing VC++6.0.
error at 0x%08X
I open up my program with a binary editor and a found about a dozen mesages about bad stuff happening at 0x%08X in the program now my question is where is 0x%08X in the memory stack and how would i find it useing VC++6.0.
> where is 0x%08X in the memory stack
It isn't anywhere, this is just a printf formatting string
At run time, if there is an error, the code will format whatever value is appropriate as 8 hex digits, with a leading 0x.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
So if there is an error there what would that mean and why would that be described as a location. My program is windows based useing direct draw and i haven't used printf in my program but stdio is included. I am useing of streams though here is the entire mesage:
with debug mode on:
Pixel DrawerWINXCLASSProgram execution begunddsd.lPitch = %ufirst surface creation failed%ldsizeof(lpddsprimary) = 0xflipfailed%p@Bp.@.BP#@.Bp(@ofstream.cpp...
@HBp.@P4@6@3@ E@B@ C@`0@1@E@D@p..Bp8@_ios.cppfilebuf1.cppB@@` D@0B@E@ E@B@ C@0j@0j@E@[email protected]\chkesp.cThe value of ESP was not properly saved across a function call. This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention. .I@:I@_file.c.[email protected]_BLOCK_TYPE_IS_VA LID(pHead->nBlockUse)ioinit.cAssertion FailedErrorWarning%s(%d) : %s
Assertion failed!Assertion failed: _CrtDbgReport: String too long or IO ErrorSecond Chance Assertion Failed: File %s, Line %d
wsprintfAuser32.dllMicrosoft Visual C++ Debug LibraryDebug %s!
Program: %s%s%s%s%s%s%s%s%s%s%s
(Press Retry to debug the application)
Module:
File:
Line:
Expression:
For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts....<program name unknown>dbgrpt.cszUserMessage != NULLClientIgnoreCRTNormalFreeError: memory allocation: bad memory block type.
Invalid allocation size: %u bytes.
%sClient hook allocation failure.
Client hook allocation failure at file %hs line %d.
dbgheap.c_CrtCheckMemory()_pFirstBlock == pOldBlock_pLastBlock == pOldBlockfRealloc || (!fRealloc && pNewBlock == pOldBlock)_BLOCK_TYPE(pOldBlock->nBlockUse)==_BLOCK_TYPE(nBlockUse)pOldBlock->nLine == IGNORE_LINE && pOldBlock->lRequest == IGNORE_REQ_CrtIsValidHeapPointer(pUserData)Allocat ion too large or negative: %u bytes.
Client hook re-allocation failure.
Client hook re-allocation failure at file %hs line %d.
_pFirstBlock == pHead_pLastBlock == pHeadpHead->nBlockUse == nBlockUsepHead->nLine == IGNORE_LINE && pHead->lRequest == IGNORE_REQDAMAGE: after %hs block (#%d) at 0x%08X.
DAMAGE: before %hs block (#%d) at 0x%08X.
Client hook free failure.
memory check error at 0x%08X = 0x%02X, should be 0x%02X.
%hs located at 0x%08X is %u bytes long.
%hs allocated at file %hs(%d).
DAMAGE: on top of Free block at 0x%08X.
DAMAGED_heapchk fails with unknown return value!
_heapchk fails with _HEAPBADPTR.
_heapchk fails with _HEAPBADEND.
_heapchk fails with _HEAPBADNODE.
_heapchk fails with _HEAPBADBEGIN.
Bad memory block found at 0x%08X.
_CrtMemCheckPoint: NULL state pointer.
_CrtMemDifference: NULL state pointer.
Object dump complete.
crt block at 0x%08X, subtype %x, %u bytes long.
normal block at 0x%08X, %u bytes long.
client block at 0x%08X, subtype %x, %u bytes long.
{%ld} %hs(%d) : #File Error#(%d) : Dumping objects ->
Data: <%s> %s
%.2X Detected memory leaks!
Total allocations: %ld bytes.
Largest number used: %ld bytes.
%ld bytes in %ld %hs Blocks.
stdenvp.cstdargv.ca_env.cruntime error
TLOSS error
SING error
DOMAIN error
R6028
- unable to initialize heap
R6027
- not enough space for lowio initialization
R6026
- not enough space for stdio initialization
R6025
- pure virtual function call
R6024
- not enough space for _onexit/atexit table
R6019
- unable to open console device
R6018
- unexpected heap error
R6017
- unexpected multithread lock error
R6016
- not enough space for thread data
abnormal program termination
R6009
- not enough space for environment
R6008
- not enough space for arguments
R6002
- floating point not loaded
Microsoft Visual C++ Runtime LibraryRuntime Error!
Program: Y..@f..@@D@Q@@@.@=@j@ L@R@.@@.@osfinfo.cchsize.csize >= 0format != NULLsprintf.cstring != NULLvsprintf.cGetLastActivePopupGetActiveWindowMes sageBoxAfclose.cstr != NULL("inconsistent IOB fields", stream->_ptr - stream->_base >= 0)_flsbuf.c..........EEE.....50P (8PX..700WP. ..`h````ppxxxx...........(null)(null)output.cch != _T('\0') A A A A A A_freebuf.cstream != NULL_getbuf.ccreateing DD objseting cooperation level to windowed mode normalC:\programming stuff\newgame\debugdump.txt
and here it is with debug mode off
runtime error
TLOSS error
SING error
DOMAIN error
R6028
- unable to initialize heap
R6027
- not enough space for lowio initialization
R6026
- not enough space for stdio initialization
R6025
- pure virtual function call
R6024
- not enough space for _onexit/atexit table
R6019
- unable to open console device
R6018
- unexpected heap error
R6017
- unexpected multithread lock error
R6016
- not enough space for thread data
abnormal program termination
R6009
- not enough space for environment
R6008
- not enough space for arguments
R6002
- floating point not loaded
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: ...<program name unknown>
SleepKERNEL32.dllDefWindowProcA.PostQuitMessage EndPaint BeginPaintDispatchMessageA.TranslateMessage.Pee kMessageAYCreateWindowExA.RegisterClassA.LoadCur sorA.LoadIconA.PostMessageAGetAsyncKeyStateUSER 32.dll_.GetStockObjectGDI32.dll.DirectDrawCreateDD RAW.dll&.GetModuleHandleAP.GetStartupInfoAGetComm andLineAt.GetVersion}ExitProcess/.RtlUnwind..GetLastError.CloseHandle.WriteFile..R eadFilej.SetFilePointerm.SetHandleCountR.GetStdHan dle..GetFileType4CreateFileA.HeapAlloc.Terminate ProcessGetCurrentProcess...UnhandledExceptionFilte r$.GetModuleFileNameAFreeEnvironmentStringsAFree EnvironmentStringsW.WideCharToMultiByte..GetEnvir onmentStrings..GetEnvironmentStringsW.HeapDestroy .HeapCreate.VirtualFree.HeapFreeFlushFileBuffe rs|.SetStdHandlea.SetEndOfFile.VirtualAlloc.Heap ReAlloc.IsBadWritePtrGetCPInfoGetACP1.GetOEMCP> .GetProcAddress.LoadLibraryA.SetUnhandledExcepti onFilter.IsBadReadPtr.IsBadCodePtr.MultiByteToW ideChar.LCMapStringA.LCMapStringWS.GetStringType AV.GetStringTypeW
oops i though it would just wrap around
> and i haven't used printf in my program
That doesn't mean the run time library can't use it.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
okay a few more questions:
first i think there is something special about 0x%08X because that was used in the section on directX debging in sunlights tutorial.
second why cand visual c++ put the error mesages in a more rational place then the EXE file(it was just by chance that i happend to look there).
> first i think there is something special about 0x%08X
Probably not - though it usually means that you've done something horribly wrong.
> second why cand visual c++ put the error mesages in a more rational place then the EXE file
Where else would they go?
I mean, for things like
R6028
- unable to initialize heap
You can look these up in the help.
Without seeing the EXACT text of the error message you got, it's hard to tell you how to go about debugging such things in future.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Its about as close to exact as you can get. I was just wondering if the program used that message say as a generic error message for something or if it was just taking up space. At any rate i think ill just restart my progam from scratch and think of the last one as a learning experiance. Oh and thanks for the help.
