On Thu, Mar 8, 2012 at 1:55 AM, Sriranga(78yrs)
<[email protected]> wrote:
> Tom,
> followed your guidance. in this connection attached screenshots for your
> perusal. CMD is still blinking for "error for loading unicharset from
> kan.unicharset. It appears crtexe.c does not exist - i dont know whether in
> operating system or part of source code of tesseract?
Ignore most of what you are seeing. It looks to me like you've Stepped
Out of your Main program function (called main()). Once that happens
it's not interesting and that's one of the reasons you don't have
source code for it.
Start over and watch carefully for which function causes that error
message about "Error loading unicharset from kan.unicharset". Anything
that happens AFTER that can be ignored, and you can just choose Debug
-> Stop Debugging (Shift+F5) from the menubar.
Just by reading the source I see:
if (!unicharset.load_from_file(unicharset_file)) {
tprintf("Error loading unicharset from %s.\n", unicharset_file);
return 1;
}
Which is exactly the error message you are seeing. So next time, step
INTO the unicharset.load_from_file() function (press F11 instead of
F10). This will then show you what load_from_file() is trying to do
and why it returns with a failure indication (in this case returns
early with False not True).
You continue doing that until it becomes obvious (hopefully) what is
going wrong. That is, step OVER functions until you find the place
where the function returns "early" with some sort of failure
indication. Stop debugging and restart the debugger, and this time
step INTO the function that last time caused an early failure
indication.
At this point you should also read the debugger documentation on
setting "Breakpoints and Tracepoints" [1]. You can tell the debugger
that you want it to run all by itself until it reaches a particular
line. That way you don't have to keep stepping manually over each line
in the program. You can let the program zip to a particular place and
stop itself when you want to start watching what happens.
HINT: It looks to me (but I may be wrong), that setting a breakpoint
at UNICHARSET::load_via_fgets() in ccutil/unicharset.cpp (line 647)
might be helpful. Then step through that function and see where it
returns false early.
You're on your own for awhile. I'll check back tomorrow to see how you
are doing. In the meantime, read the debugger documentation :)
[1] http://msdn.microsoft.com/en-us/library/ktf38f66(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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/tesseract-ocr?hl=en
