Windows debugging - WinDbg

Posted by Santhosh77 on Stack Overflow See other posts from Stack Overflow or by Santhosh77
Published on 2010-05-14T07:13:26Z Indexed on 2010/05/14 7:14 UTC
Read the original article Hit count: 249

Filed under:

Hi,

I got the following error while debuggging a process with its core dump.

0:000> !lmi test.exe Loaded Module Info: [test.exe] Module: test Base Address: 00400000 Image Name: test.exe Machine Type: 332 (I386) Time Stamp: 4a3a38ec Thu Jun 18 07:54:04 2009 Size: 27000 CheckSum: 54c30 Characteristics: 10f
Debug Data Dirs: Type Size VA Pointer MISC 110, 0, 21000 [Debug data not mapped] FPO 50, 0, 21110 [Debug data not mapped] CODEVIEW 31820, 0, 21160 [Debug data not mapped] - Can't validate symbols, if present. Image Type: FILE - Image read successfully from debugger. test.exe Symbol Type: CV - Symbols loaded successfully from image path. Load Report: cv symbols & lines

Does any body know what the error "CODEVIEW 31820, 0, 21160 [Debug data not mapped] - Can't validate symbols, if present." really mean?

Is this error meant that i can't read public/private symbols from the executable?

If it is not so, why does the WinDbg debugger throws this typr of error?

Thanks in advance, Santhosh.

© Stack Overflow or respective owner

Related posts about WinDbg