Bug#484052: tesseract segmentation fault on specific page image
2008/6/7 Chun-Chung Chen [EMAIL PROTECTED]: OK, I see that I do get the same segfault on linux-2.6.24-1-686 running testing which uses gcc-4.2.4. But, the segfault is gone on linux-2.6.25-2-amd64 running unstable which uses gcc-4.3.1 if --as-needed is left out. I am not sure if it's the gcc version or it's the architecture that made the difference. I assume that it is the architecture, as I get the segfault with or without --as-needed on gcc-4.3.1 in i386 as well. Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484052: tesseract segmentation fault on specific page image
forward 484052 http://code.google.com/p/tesseract-ocr/issues/detail?id=128 thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484052: tesseract segmentation fault on specific page image
forwarded 484052 http://code.google.com/p/tesseract-ocr/issues/detail?id=128 thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484052: tesseract segmentation fault on specific page image
Jeffrey Ratcliffe wrote: Strange. If I remove just the --as-needed, I still get the segfault. Is that the only thing you changed? OK, I see that I do get the same segfault on linux-2.6.24-1-686 running testing which uses gcc-4.2.4. But, the segfault is gone on linux-2.6.25-2-amd64 running unstable which uses gcc-4.3.1 if --as-needed is left out. I am not sure if it's the gcc version or it's the architecture that made the difference. Chun-Chung Chen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484052: tesseract segmentation fault on specific page image
2008/6/3 Chun-Chung Chen [EMAIL PROTECTED]: Ah. I was using 2.03 but compile it with just ./configure --perfix=/usr --datadir=/usr/share/tesseract-ocr; make. I found that if I remove --as-needed from the configure script options in debian/rules, I can get rid of the segmentation fault. Strange. If I remove just the --as-needed, I still get the segfault. Is that the only thing you changed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484052: tesseract segmentation fault on specific page image
2008/6/2 Chun-Chung Chen [EMAIL PROTECTED]: Tested on linux-2.6.25-2-amd64 running unstable as well as linux-2.6.24-1-686 running testing. Binary compiled from upstream source does not have this problem. I am seeing this with your test page too. However, I also see the segfault from the vanilla 2.03 release, unpatched, etc. What version of tesseract did you compile? What version of g++ are you using? Regards Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484052: tesseract segmentation fault on specific page image
Ah. I was using 2.03 but compile it with just ./configure --perfix=/usr --datadir=/usr/share/tesseract-ocr; make. I found that if I remove --as-needed from the configure script options in debian/rules, I can get rid of the segmentation fault. On Mon, 2008-06-02 at 21:20 +0200, Jeffrey Ratcliffe wrote: I am seeing this with your test page too. However, I also see the segfault from the vanilla 2.03 release, unpatched, etc. What version of tesseract did you compile? What version of g++ are you using? Regards Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
