Hello Jeff,
On Mon, 14 Jan 2013 16:36:52 -0800
Jeff Breidenbach j...@jab.org wrote:
If by very large you mean more than a gigabyte, I suggest that we
wait until you have more time. It is a lot easier for upstream to
debug and test against a smaller dataset.
Thanks for your patience
I have
Upstream says:
I think this might be a known issue that we have fixed in our
[unreleased] version.
Could do to get the svn repository up to date.
On Sun, Jan 13, 2013 at 3:25 PM, Jeff Breidenbach j...@jab.org wrote:
I don't understand what you mean by hardly trackable. The backtrace
is
Hello Jeff,
On Sat, 12 Jan 2013 20:06:19 -0800
Jeff Breidenbach j...@jab.org wrote:
Thank you for the report. Please supply data and a simple
command that reproduces the problem. The following command
(with the standard tesseract-ocr-deu-frak Debian package
installed) does not segfault for
I don't understand what you mean by hardly trackable. The backtrace
is helpful,
thank you. But also having an easy, guaranteed way to reproduce the problem
is also helpful. Is there some reason you do not wish to supply the images?
--
To UNSUBSCRIBE, email to
Thank you for the report. Please supply data and a simple
command that reproduces the problem. The following command
(with the standard tesseract-ocr-deu-frak Debian package
installed) does not segfault for me.
-Jeff
$ while true; do tesseract img028.tif img028.txt -l deu-frak; done
Tesseract
5 matches
Mail list logo
