Moses-support Digest, Vol 97, Issue 36

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. Cannot install moses, bjam failes due to not finding boost
libraries (lib64 in particular) (Daniel Seita)
2. The decoder died with 'Segmentation fault' (Huei-Chi Lin)
3. Re: The decoder died with 'Segmentation fault' (Hieu Hoang)


----------------------------------------------------------------------

Message: 1
Date: Sat, 15 Nov 2014 14:02:05 -0800
From: Daniel Seita <takeshidanny@gmail.com>
Subject: [Moses-support] Cannot install moses, bjam failes due to not
finding boost libraries (lib64 in particular)
To: moses-support@mit.edu
Message-ID:
<CAKUmyF7GXaLvrMgRXG0acF5wbgBWNUK1GEEkG-_UAnju+VzosA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello everyone,

I'm having some trouble installing boost, because it fails when running
./bjam -j8. I'm using Mac OS X 10.9.5. I have *g++* installed in:

/usr/local/bin/g++-4.9

and *boost* installed, via homebrew, in:

ls /usr/local/Cellar/boost/1.56.0/
INSTALL_RECEIPT.json include lib

Notice that the above directory has the *include *and the *lib*
directories, as required (according to bjam --help). Here is the command I
ran:

./bjam --with-boost=/usr/local/Cellar/boost/1.56.0 -j8

And I get a ton of errors that look the same, e.g.,

darwin.link
lm/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/query
ld: warning: directory not found for option
'-L/usr/local/Cellar/boost/1.56.0/lib64'
ld: library not found for -lboost_thread
clang: error: linker command failed with exit code 1 (use -v to see
invocation)

*It seems like the error is that the installer expects 'lib64' instead of
'lib'.* (Or could it be 'lib64' *and* 'lib'?) I did some searching but
wasn't sure how to get the lib64 files. Does anyone have any idea? I have
attached my build log.

Thanks,
Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141115/b2b52441/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.log.gz
Type: application/x-gzip
Size: 9627 bytes
Desc: not available
Url : http://mailman.mit.edu/mailman/private/moses-support/attachments/20141115/b2b52441/attachment-0001.bin

------------------------------

Message: 2
Date: Wed, 12 Nov 2014 15:04:04 +0100
From: Huei-Chi Lin <lin@lium.univ-lemans.fr>
Subject: [Moses-support] The decoder died with 'Segmentation fault'
To: moses-support@mit.edu
Message-ID: <546368D4.6040902@lium.univ-lemans.fr>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello,

When I ran mert-moses.pl of 2014-05-29 version, the messages
'Segmentation fault' and 'The decoder died.' were written into the log
file. This problem occurs randomly, if the mert are run several times.
Running mert within a backtracking debugger, the messages are as follows:

(gdb) exec-file /path/to/the/directory/bin/moses
(gdb) r "mert options"

Translating line 2340 in thread id 140734307309312

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff44e56700 (LWP 22396)]
0x00000000005e6625 in ?? ()

Could someone help me to resolve this problem, thanks?

best regards,
Huei-Chi Lin


------------------------------

Message: 3
Date: Sun, 16 Nov 2014 15:45:09 +0000
From: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Subject: Re: [Moses-support] The decoder died with 'Segmentation
fault'
To: Huei-Chi Lin <lin@lium.univ-lemans.fr>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbjPx5A+J6zuFKr9gPt0v4MRv7LEtN=YaN9kUPb6F0gyOg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

can you provide the exact command you ran, and the moses.ini file you used.

There was a race condition in the decoder which caused random segfaults
when multithreading was used
https://github.com/moses-smt/mosesdecoder/issues/76
However, the segfaults are rare.

This was fixed a few weeks ago. Maybe update the moses code and try running
again. If it's still a problem, let us know again and i'll try & see what
the problem is

On 12 November 2014 14:07, Huei-Chi Lin <lin@lium.univ-lemans.fr> wrote:

> Hello,
>
> When I ran mert-moses.pl of 2014-05-29 version, the messages
> 'Segmentation fault' and 'The decoder died.' were written into the log
> file. This problem occurs randomly, if the mert are run several times.
> Running mert within a backtracking debugger, the messages are as follows:
>
> (gdb) exec-file /path/to/the/directory/bin/moses
> (gdb) r "mert options"
>
> Translating line 2340 in thread id 140734307309312
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fff44e56700 (LWP 22396)]
> 0x00000000005e6625 in ?? ()
>
> Could someone help me to resolve this problem, thanks?
>
> best regards,
> Huei-Chi Lin
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>



--
Hieu Hoang
Research Associate
University of Edinburgh
http://www.hoang.co.uk/hieu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141116/70e2423d/attachment.htm

------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 97, Issue 36
*********************************************

Tweet