Dear Poly/ML experts,
I copy-pasted Motif code from "Poly/ML for Motif: Quick Reference Manual", sections 1.3 and 1.4. When I start poly session and load this code with "use" I sometimes get a Motif window but sometimes do not.
I am running polyml 5.5.2 on x86_64 Ubuntu, compiled with "--with-x --enable-shared" against Open Motif 2.3.4.
Am I missing something?
Piotr, I don't know why it would only work sometimes. Whenever I've tested it it has worked. However, the X-Windows/Motif code is very old and isn't really maintained.
David
On 31/08/2014 23:28, Piotr Trojanek wrote:
Dear Poly/ML experts,
I copy-pasted Motif code from "Poly/ML for Motif: Quick Reference Manual", sections 1.3 and 1.4. When I start poly session and load this code with "use" I sometimes get a Motif window but sometimes do not.
I am running polyml 5.5.2 on x86_64 Ubuntu, compiled with "--with-x --enable-shared" against Open Motif 2.3.4.
Am I missing something?
On Mon, Sep 1, 2014 at 1:19 PM, David Matthews <David.Matthews at prolingua.co.uk> wrote:
Piotr, I don't know why it would only work sometimes. Whenever I've tested it it has worked. However, the X-Windows/Motif code is very old and isn't really maintained.
Thanks for your reply. So far I have two workarounds: 1) use lesstif2-0.95.2-1 instead of openmotif, 2) force poly to run on a single CPU core with 'taskset -c 0 poly' (my machine has 4 cores).
Running poly with '--gcthreads 1' option does not help.
-- Piotr
David
On 31/08/2014 23:28, Piotr Trojanek wrote:
Dear Poly/ML experts,
I copy-pasted Motif code from "Poly/ML for Motif: Quick Reference Manual", sections 1.3 and 1.4. When I start poly session and load this code with "use" I sometimes get a Motif window but sometimes do not.
I am running polyml 5.5.2 on x86_64 Ubuntu, compiled with "--with-x --enable-shared" against Open Motif 2.3.4.
Am I missing something?
On 01/09/2014 13:28, Piotr Trojanek wrote:
On Mon, Sep 1, 2014 at 1:19 PM, David Matthews <David.Matthews at prolingua.co.uk> wrote:
Piotr, I don't know why it would only work sometimes. Whenever I've tested it it has worked. However, the X-Windows/Motif code is very old and isn't really maintained.
Thanks for your reply. So far I have two workarounds:
- use lesstif2-0.95.2-1 instead of openmotif,
- force poly to run on a single CPU core with 'taskset -c 0 poly' (my
machine has 4 cores).
That doesn't surprise me. I've had a quick look at the code and it does fork off a new thread in XtAppInitialise. I suspect it then could have race conditions if the subsequent Motif calls result in X-windows events being scheduled. This is much more likely if there is a second core around that can run the other thread as soon as it is unblocked.
A search with Google suggests that lesstif is thread-safe whereas openmotif isn't. I have no idea whether that is actually true or whether there is an error in the way Poly/ML uses Motif. If it works with lesstif I'd tend to stick with it.
David
-
David.Matthews＠prolingua.co.uk -
piotr.trojanek＠gmail.com