This seems to be the all-purpose way of failing when OpenMP is enabled!

I just can't run 0.4 reliably on Mac OS with OpenMP. I've ended up  
just disabling it.

Duncan

On 9 Jul 2009, at 17:23, Bill wrote:

>
> Here's the stack trace:
>
> (gdb) run page data/testimages/simple.png
> Starting program: /local/ocropus/ocropus-0.4/ocropus/ocropus page  
> data/
> testimages/simple.png
> Reading symbols for shared libraries ++++++++. done
> terminate called after throwing an instance of 'char*'
>
> Program received signal SIGABRT, Aborted.
> 0x9271de42 in __kill ()
> (gdb) bt
> #0  0x9271de42 in __kill ()
> #1  0x9271de34 in kill$UNIX2003 ()
> #2  0x9279023a in raise ()
> #3  0x9279c679 in abort ()
> #4  0x90750005 in __gnu_cxx::__verbose_terminate_handler ()
> #5  0x9074e10c in __gxx_personality_v0 ()
> #6  0x9074e06c in __gxx_personality_v0 ()
> #7  0x94b375ee in _Unwind_Backtrace ()
> #8  0x94b37a20 in _Unwind_Resume ()
> #9  0x00078afa in glinerec::LatinClassifier::outputs (this=<value
> temporarily unavailable, due to optimizations>, result=<value
> temporarily unavailable, due to optimizations>, v=<value temporarily
> unavailable, due to optimizations>) at narray.h:249
> #10 0x00095139 in glinerec::LinerecExtracted::recognizeLine
> (.omp_data_i=0xbffff1f4) at linerec.cc:556
> #11 0x0009f842 in glinerec::LinerecExtracted::recognizeLine
> (this=0x500b10, segmentatio...@0xbffff230, resu...@0x3cf9ec0,
> imag...@0xbffff420) at linerec.cc:525
> #12 0x00095f3f in ~narray [inlined] () at linerec.cc:495
> #13 0x00095f3f in ~narray [inlined] () at narray.h:242
> #14 0x00095f3f in glinerec::LinerecExtracted::recognizeLine
> (this=0x500b10, resu...@0x3cf9ec0, ima...@0xbffff420) at linerec.cc:
> 495
> #15 0x0001b017 in nustring [inlined] () at ocr-commands.cc:855
> #16 0x0001b017 in narray [inlined] () at ocr-commands.cc:142
> #17 0x0001b017 in nustring [inlined] () at narray.h:141
> #18 0x0001b017 in ocropus::main_page (argc=2, argv=0xbffff5b4) at ocr-
> commands.cc:856
> #19 0x0001be6d in ocropus::main_ocropus (argc=3, argv=0xbffff5b0) at
> ocr-commands.cc:1308
> #20 0x00005559 in main (argc=3, argv=0xbffff5b0) at ocropus.cc:38
> (gdb)
>
> On Jul 9, 9:21 am, Bill <[email protected]> wrote:
>> No, it's just that ocropus isn't respecting the configure prefix.
>> Once I symlinked /local/share/ocropus to /usr/local/share/ocropus,
>> that bug went away, and I got on to the next one.  Turns out that
>> "make install" doesn't uncompress default.fst.gz, so once again
>> ocropus fails.  Once I did that by hand, I got to the next problem,
>> which has me stumped for the moment:
>>
>> % ocropus page data/testimages/simple.png
>> terminate called after throwing an instance of 'char*'
>> Abort
>> %
>>
>> Any ideas?
>>
>> Bill
>>
>> On Jul 9, 9:06 am, Duncan McGregor <[email protected]> wrote:
>>
>>> It may be connected with a bug in the build 
>>> -http://code.google.com/p/ocropus/issues/detail?id=168
>>
>>> You need to copy data/default.model from the distribution into the
>>> required directory manually.
>>
>>> Duncan
>>
>>> On 9 Jul 2009, at 17:02, Bill Janssen wrote:
>>
>>>> OK, I'm able to build/install on OS X.  Next step is to test it.   
>>>> In
>>>> the <a href="http://code.google.com/p/ocropus/wiki/
>>>> DevInstall">DevInstall page</a>, I found the following magic
>>>> invocation:
>>
>>>> % ocropus page data/testimages/simple.png
>>
>>>> But:
>>
>>>> % ocropus page data/testimages/simple.png
>>>> FATAL: /usr/local/share/ocropus/models/default.model: failed to  
>>>> load
>>>> (/
>>>> usr/local/share/ocropus/models/default.model: cannot open file for
>>>> reading)
>>>> %
>>
>>>> Now, there IS a /local/share/ocropus/models/ directory (I  
>>>> configured
>>>> with --prefix=/local).
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to