The next release is scripted in Python and is moving more of the logic into Python, so these crashes are likely to go away.
Tom On Oct 31, 7:26 am, arnotixe <[email protected]> wrote: > Hi all I'm arnotixe, involved in tesseract for quichua development. > Just found this group, downloaded it and it works just great. > > However, the ocroscript (or something else) segfaults from time to > time, so I had to set up this cheatscript with a "this went well" > boolean variable. It works ok, but my question is: How can I debug > what part of the ocropus (or perhaps other programs, tesseract...) is > segfaulting? > > The interesting thing is, running the ocroscript serveral times on the > exact same file ... doesn't always segfault. Eventually it succeeds. > =?? > > for a in $i/???.jpg; do > readok=false > while ( ! $readok ); do > echo Reading $a > ocroscript rec-tess $a > tmp.html && readok=true > done > cat tmp.html >>$book.html > done > > I don't think it's a memory problem, although I'm no linux guru: > $ free -m > total used free shared buffers > cached > Mem: 2012 1566 445 0 34 > 494 > -/+ buffers/cache: 1037 974 > Swap: 5890 158 5732 -- You received this message because you are subscribed to the Google Groups "ocropus" 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/ocropus?hl=en.
