On Thu, Mar 8, 2012 at 12:31 AM, Sriranga(78yrs) <withblessing.sriranga.1...@gmail.com> wrote: > TP, > tried again and successfully displayed as follow: > Extract of output of VS2008 is reproduced below: > 'dawg2wordlistd.exe': Loaded > 'M:\r700\BuildFolder\tesseract-ocr\vs2008\LIB_Debug\dawg2wordlistd.exe', > Symbols loaded. > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\ntdll.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll' > 'dawg2wordlistd.exe': Loaded > 'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456\msvcr90d.dll' > 'dawg2wordlistd.exe': Loaded > 'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456\msvcp90d.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\ws2_32.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\secur32.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\msvcrt.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\ws2help.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\user32.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\gdi32.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\imm32.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\lpk.dll' > 'dawg2wordlistd.exe': Loaded 'C:\WINDOWS\system32\usp10.dll' > The program '[3292] dawg2wordlistd.exe: Native' has exited with code 1 > (0x1).
That's what it looks like when your program runs without crashing. Although the convention is to return 0 for success. Okay, now that you seem to be able to run the debugger, instead of choosing Debug -> Start new instance, try doing Debug -> Step into new instance. The debugger will load dawg2wordlist and you'll see those messages again as it does it. Then the debugger will Pause and let you look around at stuff, but more importantly it will let you execute dawg2wordlist LINE by LINE. So... press the F10 function key or choose Debug -> Step Over from the menu bar to execute dawg2wordlist one line at a time. When you get to something that looks like this: if (!unicharset.load_from_file(unicharset_file)) thats a function call, and you can instead press the F11 function key or choose Debug -> Step Into to see what that function is going to do. If you instead press F10 at this point you "Step Over" that function and don't get to see all the details of what it does (which is sometimes what you want). For example, you don't really need to see everything that the tprintf() function does to print a message on the screen, so you would normally press F10 to Step Over the tprintf() function call. dawg2wordlist isn't very long (at least at the top level), so it should be *very* instructive to step through it line by line and see how it works. Remember to look at the hidden command prompt window occasionally to see if any messages have been printed out by dawg2wordlist. For more info see the VS2008 documentation on "Execution Control" [1] and "Viewing Data in the Debugger" [2], and especially "Variable Windows" [3]. [1] http://msdn.microsoft.com/en-us/library/y740d9d3(v=vs.90).aspx [2] http://msdn.microsoft.com/en-us/library/esta7c62(v=vs.90).aspx [3] http://msdn.microsoft.com/en-us/library/4dt5w8ta(v=vs.90).aspx -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to tesseract-ocr@googlegroups.com To unsubscribe from this group, send email to tesseract-ocr+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en
