On Apr 12, 5:22 pm, Zdenko Podobný <[email protected]> wrote: > Dňa 12.04.2012 18:09, Falke wrote / napísal(a):> i hope this posts in the > right order > > > addendum to my reply from 30 minutes ago: I rebuilt the bad build. > > Didn't help; same error. > > Does it mean it segfaults? Can you provide more info (OS, platform, how > you run OCR...)? > > I tried it (tesseract segfault_trigger.jpg segfault_trigger) on openSUSE > 12.1 (x86_64) and windows XP SP3 (32bit) and I have no problem. > > Did you modified source? If yes, can you please test unmodified source? >
Guys! humans: 0 machines: 1 my messages were posted (by the human moderators :-) in the wrong chronological order (effectively like "top posting"?) To answer Zdenko: Yes, it still segfaults. The rebuilding did not help. I did not modify the code. (Even though I desperately need/want to (pertaining to box file printout and bold/italic/font1/font2 printout, upon recognition) So, this is a total mystery, at this point. A while ago I mentioned I was dealing with two Ubuntu 10.10 systems -- on one I had compile failures, on the other the compile went through. I ended up solving it. Well, the success/failure is now reversed -- the system that failed to compile back then, now gives me no errors with 3.02. The other one, which didn't have the compile failure gives me the runtime segfault. Perhaps I should also say that the failing build/system seems to fail SPORADICALLY, selectively -- I extracted a bunch of pgm files using subtitle2pgm. My bad build recognized MOST of them, but segfaulted on a few of them -- (from the same set!) thanks again > Zdenko -- 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
