Smalltalk › Pharo › Pharo Smalltalk Developers

Segmentation fault while installing Scale

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

14 messages Options

Andrey Tykhonov

Segmentation fault while installing Scale

Hi all!

While executing the following command:

$ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > stderr.log

I got the Segmentation fault error. You can see it in the contents of

stderr.log which is attached to the email. Here you can see the

output of the mentioned command:

```

--2017-02-03 19:35:16-- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh

Resolving raw.githubusercontent.com... 151.101.128.133, 151.101.192.133, 151.101.64.133, ...

Connecting to raw.githubusercontent.com|151.101.128.133|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 1021 [text/plain]

Saving to: ‘STDOUT’

- 100%[=============================================================>] 1021 --.-KB/s in 0s

2017-02-03 19:35:16 (274 MB/s) - written to stdout [1021/1021]

Cloning into '/tmp/scale'...

remote: Counting objects: 1457, done.

remote: Total 1457 (delta 0), reused 0 (delta 0), pack-reused 1457

Receiving objects: 100% (1457/1457), 656.60 KiB | 714.00 KiB/s, done.

Resolving deltas: 100% (799/799), done.

Note: checking out 'f70fdb90cf66d443140b6fe84cad9848163bf32e'.

You are in 'detached HEAD' state. You can look around, make experimental

changes and commit them, and you can discard any commits you make in this

state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may

do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

--2017-02-03 19:35:18-- http://get.pharo.org/50+vm

Resolving get.pharo.org... 128.93.162.72

Connecting to get.pharo.org|128.93.162.72|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 2901 (2.8K) [text/html]

Saving to: ‘STDOUT’

- 100%[=============================================================>] 2.83K --.-KB/s in 0.001s

2017-02-03 19:35:18 (3.56 MB/s) - written to stdout [2901/2901]

Downloading the latest 50 Image:

http://files.pharo.org/get-files/50/pharo.zip

Downloading the latest pharoVM:

http://files.pharo.org/get-files/50/pharo-linux-stable.zip

Downloading PharoV50.sources:

http://files.pharo.org/get-files/50/sources.zip

Creating starter scripts pharo and pharo-ui

Fetched -> BaselineOfScale-SantiagoBragagnolo.4 --- filetree:///tmp/scale/src [:] --- filetree:///tmp/scale/src./pharo: line 11: 19176 Aborted "$DIR"/"pharo-vm/pharo" --nodisplay "$@"

Syntax Error on line 26: 'Unmatched '' in string literal. ->'

=============================================================

01: | scapeParentDirectory pharoParentDirectory scaleX scaleuiX |

02:

03: system stdout << 'Uninstalling scale' << String cr.

04:

05: system saveImageAs: #/ asFileReference / #tmp / #'uninstall.image'.

06: " The image must be stored elsewhere for deleting all the files "

07:

08: scaleX := '/usr/local/bin/scale' asFileReference.

09: scaleX exists ifTrue: [ system call: ' rm ', scaleX fullName ].

10: system stdout << 'Uninstalling executable scale' << String cr ; flush.

11:

12: scaleuiX:='/usr/local/bin/scale-ui' asFileReference.

13: scaleuiX exists ifTrue: [ system call: ' rm ', scaleuiX fullName ].

14: system stdout << 'Uninstalling executable scale-ui' << String cr ; flush.

15:

16: scapeParentDirectory := '/usr/local/scale' asFileReference.

17: pharoParentDirectory := '/usr/local/pharo' asFileReference.

18:

19: scapeParentDirectory exists ifTrue: [ system call: ' rm -rf ', scapeParentDirectory fullName ].

20: system stdout << 'Removing scale folder' << String cr ; flush.

21:

22: pharoParentDirectory exists ifTrue: [ system call: ' rm -rf ', pharoParentDirectory fullName ].

23: system stdout << 'Removing pharo folder' << String cr ; flush.

24:

25:

26: system stdout << 'Done

_^_

Syntax Error on line 39: 'Unmatched '' in string literal. ->'

=============================================================

01: | scaleParentDirectory scaleFile scaleUIFile pharoParentDirectory|

02:

03: " DEPLOY "

04: system stdout << 'Deploying scale command';cr.

05:

06: scaleParentDirectory := '/usr/local/scale' asFileReference.

07:

08: scaleParentDirectory exists

09: ifTrue: [

10: system stderr << 'There is already an installation. Please uninstall before'

11: ] ifFalse: [

12: scaleParentDirectory ensureCreateDirectory.

13: scaleFile := scaleParentDirectory / 'scale'.

14: scaleUIFile := scaleParentDirectory / 'scale-ui'.

15: system workingDirectory / '..' / 'scale' copyTo: scaleFile.

16: system workingDirectory / '..' / 'scale-ui' copyTo: scaleUIFile.

17: system workingDirectory / '..' / #build / 'uninstall.st' copyTo: scaleParentDirectory / 'uninstall.st'.

18: system stdout << 'Deploying Pharo';cr.

19:

20: pharoParentDirectory := '/usr/local/pharo' asFileReference.

21: pharoParentDirectory ensureCreateDirectory.

22: #( 'pharo' 'pharo-vm' 'pharo-ui')

23: do: [ :file | system workingDirectory / file copyAllTo: pharoParentDirectory / file ].

24:

25: #( 'Pharo.image' 'Pharo.changes')

26: do: [ :file | system workingDirectory / file copyAllTo: scaleParentDirectory / file ].

27:

28:

29: system stdout << 'Giving permissions to run';cr.

30:

31: system call: 'chmod +x ', (pharoParentDirectory / 'pharo') fullName.

32: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-ui') fullName.

33: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-vm/pharo') fullName.

34: system call: 'chmod +x ', (scaleParentDirectory / 'uninstall.st') fullName.

35: system call: 'chmod +x ', scaleFile fullName.

36: system call: 'chmod +x ', scaleUIFile fullName.

37: system ln: scaleFile to: '/usr/local/bin/scale' asFileReference.

38: system ln: scaleUIFile to: '/usr/local/bin/scale-ui' asFileReference.

39: system stdout << 'Done

_^_

```

Could you please help me find a workaround in order to bypass this issue?

Thank you in advance!

Andriy

stderr.log (71K) Download Attachment

Stephane Ducasse-3

Re: Segmentation fault while installing Scale

Hi andrey

can you tell us on which OS and version and which VM do you use (there is a System report browser where you can find the information.

On Mon, Feb 6, 2017 at 8:20 PM, Andrey Tykhonov <[hidden email]> wrote:

Hi all!

While executing the following command:

$ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > stderr.log

I got the Segmentation fault error. You can see it in the contents of
stderr.log which is attached to the email. Here you can see the
output of the mentioned command:

```
--2017-02-03 19:35:16-- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh
Resolving raw.githubusercontent.com... 151.101.128.133, 151.101.192.133, 151.101.64.133, ...
Connecting to raw.githubusercontent.com|151.101.128.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1021 [text/plain]
Saving to: ‘STDOUT’

- 100%[=============================================================>] 1021 --.-KB/s in 0s

2017-02-03 19:35:16 (274 MB/s) - written to stdout [1021/1021]

Cloning into '/tmp/scale'...
remote: Counting objects: 1457, done.
remote: Total 1457 (delta 0), reused 0 (delta 0), pack-reused 1457
Receiving objects: 100% (1457/1457), 656.60 KiB | 714.00 KiB/s, done.
Resolving deltas: 100% (799/799), done.
Note: checking out 'f70fdb90cf66d443140b6fe84cad9848163bf32e'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

--2017-02-03 19:35:18-- http://get.pharo.org/50+vm
Resolving get.pharo.org... 128.93.162.72
Connecting to get.pharo.org|128.93.162.72|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2901 (2.8K) [text/html]
Saving to: ‘STDOUT’

- 100%[=============================================================>] 2.83K --.-KB/s in 0.001s

2017-02-03 19:35:18 (3.56 MB/s) - written to stdout [2901/2901]

Downloading the latest 50 Image:
http://files.pharo.org/get-files/50/pharo.zip
Downloading the latest pharoVM:
http://files.pharo.org/get-files/50/pharo-linux-stable.zip
Downloading PharoV50.sources:
http://files.pharo.org/get-files/50/sources.zip
Creating starter scripts pharo and pharo-ui

Fetched -> BaselineOfScale-SantiagoBragagnolo.4 --- filetree:///tmp/scale/src [:] --- filetree:///tmp/scale/src./pharo: line 11: 19176 Aborted "$DIR"/"pharo-vm/pharo" --nodisplay "$@"
Syntax Error on line 26: 'Unmatched '' in string literal. ->'
=============================================================
01: | scapeParentDirectory pharoParentDirectory scaleX scaleuiX |
02:
03: system stdout << 'Uninstalling scale' << String cr.
04:
05: system saveImageAs: #/ asFileReference / #tmp / #'uninstall.image'.
06: " The image must be stored elsewhere for deleting all the files "
07:
08: scaleX := '/usr/local/bin/scale' asFileReference.
09: scaleX exists ifTrue: [ system call: ' rm ', scaleX fullName ].
10: system stdout << 'Uninstalling executable scale' << String cr ; flush.
11:
12: scaleuiX:='/usr/local/bin/scale-ui' asFileReference.
13: scaleuiX exists ifTrue: [ system call: ' rm ', scaleuiX fullName ].
14: system stdout << 'Uninstalling executable scale-ui' << String cr ; flush.
15:
16: scapeParentDirectory := '/usr/local/scale' asFileReference.
17: pharoParentDirectory := '/usr/local/pharo' asFileReference.
18:
19: scapeParentDirectory exists ifTrue: [ system call: ' rm -rf ', scapeParentDirectory fullName ].
20: system stdout << 'Removing scale folder' << String cr ; flush.
21:
22: pharoParentDirectory exists ifTrue: [ system call: ' rm -rf ', pharoParentDirectory fullName ].
23: system stdout << 'Removing pharo folder' << String cr ; flush.
24:
25:
26: system stdout << 'Done
_^_
Syntax Error on line 39: 'Unmatched '' in string literal. ->'
=============================================================
01: | scaleParentDirectory scaleFile scaleUIFile pharoParentDirectory|
02:
03: " DEPLOY "
04: system stdout << 'Deploying scale command';cr.
05:
06: scaleParentDirectory := '/usr/local/scale' asFileReference.
07:
08: scaleParentDirectory exists
09: ifTrue: [
10: system stderr << 'There is already an installation. Please uninstall before'
11: ] ifFalse: [
12: scaleParentDirectory ensureCreateDirectory.
13: scaleFile := scaleParentDirectory / 'scale'.
14: scaleUIFile := scaleParentDirectory / 'scale-ui'.
15: system workingDirectory / '..' / 'scale' copyTo: scaleFile.
16: system workingDirectory / '..' / 'scale-ui' copyTo: scaleUIFile.
17: system workingDirectory / '..' / #build / 'uninstall.st' copyTo: scaleParentDirectory / 'uninstall.st'.
18: system stdout << 'Deploying Pharo';cr.
19:
20: pharoParentDirectory := '/usr/local/pharo' asFileReference.
21: pharoParentDirectory ensureCreateDirectory.
22: #( 'pharo' 'pharo-vm' 'pharo-ui')
23: do: [ :file | system workingDirectory / file copyAllTo: pharoParentDirectory / file ].
24:
25: #( 'Pharo.image' 'Pharo.changes')
26: do: [ :file | system workingDirectory / file copyAllTo: scaleParentDirectory / file ].
27:
28:
29: system stdout << 'Giving permissions to run';cr.
30:
31: system call: 'chmod +x ', (pharoParentDirectory / 'pharo') fullName.
32: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-ui') fullName.
33: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-vm/pharo') fullName.
34: system call: 'chmod +x ', (scaleParentDirectory / 'uninstall.st') fullName.
35: system call: 'chmod +x ', scaleFile fullName.
36: system call: 'chmod +x ', scaleUIFile fullName.
37: system ln: scaleFile to: '/usr/local/bin/scale' asFileReference.
38: system ln: scaleUIFile to: '/usr/local/bin/scale-ui' asFileReference.
39: system stdout << 'Done
_^_
```

Could you please help me find a workaround in order to bypass this issue?

Thank you in advance!

--
Andriy

Clément Béra

Re: Segmentation fault while installing Scale

Hi Andrey,

Thanks for providing both a way to reproduce and the log so we can have you machine details. I see that the VM was compiled from build #589 on jenkins with VMMaker.oscog-eem.1855 and you're on Linux using x86 back-end.

Scale works only on Linux and when I try the wget command from Mac it does not work so I can't reproduce right now.

I suggest that for now you try to use one of the newer VMs (from http://files.pharo.org/vm/pharo-spur32/linux/ , you're using stable-20160504.zip, pick another one, I suggest a more recent one than from May last year, either stable-20160623.zip or pharo-linux-i386itimer-201702061308-aa78f27.zip) and then use the "classic installation" to be able to use another VM than the one downloaded by the wget script until someone can have a look into your problem.

Best,

Clement

On Tue, Feb 7, 2017 at 8:00 AM, Stephane Ducasse <[hidden email]> wrote:

Hi andrey

can you tell us on which OS and version and which VM do you use (there is a System report browser where you can find the information.

Tx

On Mon, Feb 6, 2017 at 8:20 PM, Andrey Tykhonov <[hidden email]> wrote:
Hi all!

While executing the following command:

$ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > stderr.log

I got the Segmentation fault error. You can see it in the contents of
stderr.log which is attached to the email. Here you can see the
output of the mentioned command:

```
--2017-02-03 19:35:16-- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh
Resolving raw.githubusercontent.com... 151.101.128.133, 151.101.192.133, 151.101.64.133, ...
Connecting to raw.githubusercontent.com|151.101.128.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1021 [text/plain]
Saving to: ‘STDOUT’

- 100%[=============================================================>] 1021 --.-KB/s in 0s

2017-02-03 19:35:16 (274 MB/s) - written to stdout [1021/1021]

Cloning into '/tmp/scale'...
remote: Counting objects: 1457, done.
remote: Total 1457 (delta 0), reused 0 (delta 0), pack-reused 1457
Receiving objects: 100% (1457/1457), 656.60 KiB | 714.00 KiB/s, done.
Resolving deltas: 100% (799/799), done.
Note: checking out 'f70fdb90cf66d443140b6fe84cad9848163bf32e'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

--2017-02-03 19:35:18-- http://get.pharo.org/50+vm
Resolving get.pharo.org... 128.93.162.72
Connecting to get.pharo.org|128.93.162.72|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2901 (2.8K) [text/html]
Saving to: ‘STDOUT’

- 100%[=============================================================>] 2.83K --.-KB/s in 0.001s

2017-02-03 19:35:18 (3.56 MB/s) - written to stdout [2901/2901]

Downloading the latest 50 Image:
http://files.pharo.org/get-files/50/pharo.zip
Downloading the latest pharoVM:
http://files.pharo.org/get-files/50/pharo-linux-stable.zip
Downloading PharoV50.sources:
http://files.pharo.org/get-files/50/sources.zip
Creating starter scripts pharo and pharo-ui

Fetched -> BaselineOfScale-SantiagoBragagnolo.4 --- filetree:///tmp/scale/src [:] --- filetree:///tmp/scale/src./pharo: line 11: 19176 Aborted "$DIR"/"pharo-vm/pharo" --nodisplay "$@"
Syntax Error on line 26: 'Unmatched '' in string literal. ->'
=============================================================
01: | scapeParentDirectory pharoParentDirectory scaleX scaleuiX |
02:
03: system stdout << 'Uninstalling scale' << String cr.
04:
05: system saveImageAs: #/ asFileReference / #tmp / #'uninstall.image'.
06: " The image must be stored elsewhere for deleting all the files "
07:
08: scaleX := '/usr/local/bin/scale' asFileReference.
09: scaleX exists ifTrue: [ system call: ' rm ', scaleX fullName ].
10: system stdout << 'Uninstalling executable scale' << String cr ; flush.
11:
12: scaleuiX:='/usr/local/bin/scale-ui' asFileReference.
13: scaleuiX exists ifTrue: [ system call: ' rm ', scaleuiX fullName ].
14: system stdout << 'Uninstalling executable scale-ui' << String cr ; flush.
15:
16: scapeParentDirectory := '/usr/local/scale' asFileReference.
17: pharoParentDirectory := '/usr/local/pharo' asFileReference.
18:
19: scapeParentDirectory exists ifTrue: [ system call: ' rm -rf ', scapeParentDirectory fullName ].
20: system stdout << 'Removing scale folder' << String cr ; flush.
21:
22: pharoParentDirectory exists ifTrue: [ system call: ' rm -rf ', pharoParentDirectory fullName ].
23: system stdout << 'Removing pharo folder' << String cr ; flush.
24:
25:
26: system stdout << 'Done
_^_
Syntax Error on line 39: 'Unmatched '' in string literal. ->'
=============================================================
01: | scaleParentDirectory scaleFile scaleUIFile pharoParentDirectory|
02:
03: " DEPLOY "
04: system stdout << 'Deploying scale command';cr.
05:
06: scaleParentDirectory := '/usr/local/scale' asFileReference.
07:
08: scaleParentDirectory exists
09: ifTrue: [
10: system stderr << 'There is already an installation. Please uninstall before'
11: ] ifFalse: [
12: scaleParentDirectory ensureCreateDirectory.
13: scaleFile := scaleParentDirectory / 'scale'.
14: scaleUIFile := scaleParentDirectory / 'scale-ui'.
15: system workingDirectory / '..' / 'scale' copyTo: scaleFile.
16: system workingDirectory / '..' / 'scale-ui' copyTo: scaleUIFile.
17: system workingDirectory / '..' / #build / 'uninstall.st' copyTo: scaleParentDirectory / 'uninstall.st'.
18: system stdout << 'Deploying Pharo';cr.
19:
20: pharoParentDirectory := '/usr/local/pharo' asFileReference.
21: pharoParentDirectory ensureCreateDirectory.
22: #( 'pharo' 'pharo-vm' 'pharo-ui')
23: do: [ :file | system workingDirectory / file copyAllTo: pharoParentDirectory / file ].
24:
25: #( 'Pharo.image' 'Pharo.changes')
26: do: [ :file | system workingDirectory / file copyAllTo: scaleParentDirectory / file ].
27:
28:
29: system stdout << 'Giving permissions to run';cr.
30:
31: system call: 'chmod +x ', (pharoParentDirectory / 'pharo') fullName.
32: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-ui') fullName.
33: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-vm/pharo') fullName.
34: system call: 'chmod +x ', (scaleParentDirectory / 'uninstall.st') fullName.
35: system call: 'chmod +x ', scaleFile fullName.
36: system call: 'chmod +x ', scaleUIFile fullName.
37: system ln: scaleFile to: '/usr/local/bin/scale' asFileReference.
38: system ln: scaleUIFile to: '/usr/local/bin/scale-ui' asFileReference.
39: system stdout << 'Done
_^_
```

Could you please help me find a workaround in order to bypass this issue?

Thank you in advance!

--
Andriy

Guillermo Polito

Re: Segmentation fault while installing Scale

Hi,

We are looking at it with Santi. I see in the log that you're using an ubuntu 12?

I tried in a debian jessie and Santi in an ubuntu 14 and we could not reproduce it. Also the travis ci of scale uses ubuntu 12 and the installation works in there...

Could you give more details about your system?

Thanks,

Guille and Santi

On Tue, Feb 7, 2017 at 8:43 AM, Clément Bera <[hidden email]> wrote:

Hi Andrey,

Thanks for providing both a way to reproduce and the log so we can have you machine details. I see that the VM was compiled from build #589 on jenkins with VMMaker.oscog-eem.1855 and you're on Linux using x86 back-end.

Scale works only on Linux and when I try the wget command from Mac it does not work so I can't reproduce right now.

I suggest that for now you try to use one of the newer VMs (from http://files.pharo.org/vm/pharo-spur32/linux/ , you're using stable-20160504.zip, pick another one, I suggest a more recent one than from May last year, either stable-20160623.zip or pharo-linux-i386itimer-201702061308-aa78f27.zip) and then use the "classic installation" to be able to use another VM than the one downloaded by the wget script until someone can have a look into your problem.

Best,

Clement

On Tue, Feb 7, 2017 at 8:00 AM, Stephane Ducasse <[hidden email]> wrote:
Hi andrey

can you tell us on which OS and version and which VM do you use (there is a System report browser where you can find the information.

Tx

On Mon, Feb 6, 2017 at 8:20 PM, Andrey Tykhonov <[hidden email]> wrote:
Hi all!

While executing the following command:

$ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > stderr.log

I got the Segmentation fault error. You can see it in the contents of
stderr.log which is attached to the email. Here you can see the
output of the mentioned command:

```
--2017-02-03 19:35:16-- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh
Resolving raw.githubusercontent.com... 151.101.128.133, 151.101.192.133, 151.101.64.133, ...
Connecting to raw.githubusercontent.com|151.101.128.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1021 [text/plain]
Saving to: ‘STDOUT’

- 100%[=============================================================>] 1021 --.-KB/s in 0s

2017-02-03 19:35:16 (274 MB/s) - written to stdout [1021/1021]

Cloning into '/tmp/scale'...
remote: Counting objects: 1457, done.
remote: Total 1457 (delta 0), reused 0 (delta 0), pack-reused 1457
Receiving objects: 100% (1457/1457), 656.60 KiB | 714.00 KiB/s, done.
Resolving deltas: 100% (799/799), done.
Note: checking out 'f70fdb90cf66d443140b6fe84cad9848163bf32e'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

--2017-02-03 19:35:18-- http://get.pharo.org/50+vm
Resolving get.pharo.org... 128.93.162.72
Connecting to get.pharo.org|128.93.162.72|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2901 (2.8K) [text/html]
Saving to: ‘STDOUT’

- 100%[=============================================================>] 2.83K --.-KB/s in 0.001s

2017-02-03 19:35:18 (3.56 MB/s) - written to stdout [2901/2901]

Downloading the latest 50 Image:
http://files.pharo.org/get-files/50/pharo.zip
Downloading the latest pharoVM:
http://files.pharo.org/get-files/50/pharo-linux-stable.zip
Downloading PharoV50.sources:
http://files.pharo.org/get-files/50/sources.zip
Creating starter scripts pharo and pharo-ui

Fetched -> BaselineOfScale-SantiagoBragagnolo.4 --- filetree:///tmp/scale/src [:] --- filetree:///tmp/scale/src./pharo: line 11: 19176 Aborted "$DIR"/"pharo-vm/pharo" --nodisplay "$@"
Syntax Error on line 26: 'Unmatched '' in string literal. ->'
=============================================================
01: | scapeParentDirectory pharoParentDirectory scaleX scaleuiX |
02:
03: system stdout << 'Uninstalling scale' << String cr.
04:
05: system saveImageAs: #/ asFileReference / #tmp / #'uninstall.image'.
06: " The image must be stored elsewhere for deleting all the files "
07:
08: scaleX := '/usr/local/bin/scale' asFileReference.
09: scaleX exists ifTrue: [ system call: ' rm ', scaleX fullName ].
10: system stdout << 'Uninstalling executable scale' << String cr ; flush.
11:
12: scaleuiX:='/usr/local/bin/scale-ui' asFileReference.
13: scaleuiX exists ifTrue: [ system call: ' rm ', scaleuiX fullName ].
14: system stdout << 'Uninstalling executable scale-ui' << String cr ; flush.
15:
16: scapeParentDirectory := '/usr/local/scale' asFileReference.
17: pharoParentDirectory := '/usr/local/pharo' asFileReference.
18:
19: scapeParentDirectory exists ifTrue: [ system call: ' rm -rf ', scapeParentDirectory fullName ].
20: system stdout << 'Removing scale folder' << String cr ; flush.
21:
22: pharoParentDirectory exists ifTrue: [ system call: ' rm -rf ', pharoParentDirectory fullName ].
23: system stdout << 'Removing pharo folder' << String cr ; flush.
24:
25:
26: system stdout << 'Done
_^_
Syntax Error on line 39: 'Unmatched '' in string literal. ->'
=============================================================
01: | scaleParentDirectory scaleFile scaleUIFile pharoParentDirectory|
02:
03: " DEPLOY "
04: system stdout << 'Deploying scale command';cr.
05:
06: scaleParentDirectory := '/usr/local/scale' asFileReference.
07:
08: scaleParentDirectory exists
09: ifTrue: [
10: system stderr << 'There is already an installation. Please uninstall before'
11: ] ifFalse: [
12: scaleParentDirectory ensureCreateDirectory.
13: scaleFile := scaleParentDirectory / 'scale'.
14: scaleUIFile := scaleParentDirectory / 'scale-ui'.
15: system workingDirectory / '..' / 'scale' copyTo: scaleFile.
16: system workingDirectory / '..' / 'scale-ui' copyTo: scaleUIFile.
17: system workingDirectory / '..' / #build / 'uninstall.st' copyTo: scaleParentDirectory / 'uninstall.st'.
18: system stdout << 'Deploying Pharo';cr.
19:
20: pharoParentDirectory := '/usr/local/pharo' asFileReference.
21: pharoParentDirectory ensureCreateDirectory.
22: #( 'pharo' 'pharo-vm' 'pharo-ui')
23: do: [ :file | system workingDirectory / file copyAllTo: pharoParentDirectory / file ].
24:
25: #( 'Pharo.image' 'Pharo.changes')
26: do: [ :file | system workingDirectory / file copyAllTo: scaleParentDirectory / file ].
27:
28:
29: system stdout << 'Giving permissions to run';cr.
30:
31: system call: 'chmod +x ', (pharoParentDirectory / 'pharo') fullName.
32: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-ui') fullName.
33: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-vm/pharo') fullName.
34: system call: 'chmod +x ', (scaleParentDirectory / 'uninstall.st') fullName.
35: system call: 'chmod +x ', scaleFile fullName.
36: system call: 'chmod +x ', scaleUIFile fullName.
37: system ln: scaleFile to: '/usr/local/bin/scale' asFileReference.
38: system ln: scaleUIFile to: '/usr/local/bin/scale-ui' asFileReference.
39: system stdout << 'Done
_^_
```

Could you please help me find a workaround in order to bypass this issue?

Thank you in advance!

--
Andriy

Andrey Tykhonov

Re: Segmentation fault while installing Scale

In reply to this post by Andrey Tykhonov

Hi stephane

> can you tell us on which OS and version

This is Gentoo Linux. There is no such a thing like a version. There are kernel and a lot of software.

Kernel version:

# uname -a

Linux tp 4.9.6-gentoo #1 SMP Thu Jan 26 17:04:47 EET 2017 x86_64 Intel(R) Core(TM) i7-6700HQ CPU @ 2 I found crash.dmp near pharo-ui,.60GHz GenuineIntel GNU/Linux

Let me know please if I could provide more info on this matter.

> and which VM do you use (there is a System report browser where you can find the information.

It is downloaded by means of the command:

wget -O - get.pharo.org/50+vm | bash

AFAIU, the latest VM is downloaded by means of this command. I opened pharo-ui:

./pharo-ui Pharo.image > pharo.log

and it was opened for a while, but it crashed when I tried to get information from System report browser. After that, I cannot open pharo-ui anymore. Two log files are attached to this email.

Best regards,

Andriy

crash.dmp (103K) Download Attachment

pharo.log (66K) Download Attachment

Andrey Tykhonov

Re: Segmentation fault while installing Scale

In reply to this post by Andrey Tykhonov

Hi Clement,

> Hi Andrey,

> Thanks for providing both a way to reproduce and the log so we can have you

> machine details. I see that the VM was compiled from build #589 on jenkins

> with VMMaker.oscog-eem.1855 and you're on Linux using x86 back-end.

> Scale works only on Linux and when I try the wget command from Mac it does

> not work so I can't reproduce right now.

> I suggest that for now you try to use one of the newer VMs (from

> http://files.pharo.org/vm/pharo-spur32/linux/ , you're

> using stable-20160504.zip, pick another one,

It seems, the latest VM is downloaded. It is downloaded by means of

the following command:

wget -O - get.pharo.org/50+vm | bash

Does it download old VM. Is this script outdated?

I suggest a more recent one

> than from May last year, either stable-20160623.zip

> or pharo-linux-i386itimer-201702061308-aa78f27.zip) and then use the

> "classic installation" to be able to use another VM than the one downloaded

> by the wget script until someone can have a look into your problem.

Could you please help, where could I get Pharo.image file which is

required to execute pharo/pharo-ui? If I use existing one (with a VM

taken from either stable-20160623.zip or

pharo-linux-i386itimer-201702061308-aa78f27.zip), the VM crashes. So,

it seems, I need another Pharo.image as well, right?

With the best regards,

Andriy

Andrey Tykhonov

Re: Segmentation fault while installing Scale

In reply to this post by Andrey Tykhonov

Hello,

> Hi,

> We are looking at it with Santi. I see in the log that you're using an

ubuntu 12?

No, this is Gentoo Linux.

> I tried in a debian jessie and Santi in an ubuntu 14 and we could not

> reproduce it. Also the travis ci of scale uses ubuntu 12 and the

> installation works in there...

> Could you give more details about your system?

Sure, but I'm not sure which exactly information will be useful, so,

please clarify. For now, I'm sending you kernel version:

$ uname -a

Linux tp 4.9.6-gentoo #1 SMP Thu Jan 26 17:04:47 EET 2017 x86_64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz GenuineIntel GNU/Linux

> Thanks, Guille and Santi

Thank you!

Andriy

Andrey Tykhonov

Re: Segmentation fault while installing Scale

In reply to this post by Andrey Tykhonov

Hi all,

> and which VM do you use (there is a System report browser where you can find the information.

I've somehow managed to get the information from System report browser:

Image

-----

/home/demi/mess/2017/06/tmp2/Pharo.image

Pharo5.0

Latest update: #50768

Unnamed

Virtual Machine

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

/home/demi/mess/2017/06/tmp2/pharo-vm/pharo

CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016

StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016

https://github.com/pharo-project/pharo-vm.git Commit: b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By: Esteban Lorenzano <[hidden email]> Jenkins build #589

Unix built on May 4 2016 11:54:41 Compiler: 4.6.3

VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit: b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By: Esteban Lorenzano <[hidden email]> Jenkins build #589

CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016

StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016

I noticed that there are more items which could be selected (list in the left bar, I mean System report browser), but I cannot get more info, because pharo crashes each time I try to select all text from the all items. May be it would be helpful (and I'll be able to) to get information only from some particular item? But then, I need to know which exactly items would be helpful.

Also, I'm attaching to this email log file after execution of the Pharo with strace:

strace ./pharo-ui Pharo.image > pharo-ui-with-strace.log 2>&1

I hope it could shed more light on the issue.

pharo-ui-with-strace.log (46K) Download Attachment

Ben Coman

Re: Segmentation fault while installing Scale

Are you on 64-bit using 32-bit Pharo?
Can you use ldd to check the pharo binary is linking to these 32-bit libraries?
http://pharo.org/gnu-linux-installation

When you get it working can you provide a recipe for the download page.

Alternatively you might try either (pre-release) 64-bit VM from...
http://files.pharo.org/vm/pharo-spur64/linux/
* pharo-linux-x86_64threaded-201702061308-aa78f27.zip
* pharo-linux-x86_64itimer-201702030802-61970b6.zip
http://forum.world.st/Unix-heartbeat-thread-vs-itimer-td4928943.html

and just expand the image zip in the same folder...
http://files.pharo.org/image/60/
* 60385-64.zip

cheers -ben

On Sat, Feb 11, 2017 at 5:49 AM, Andrey Tykhonov <[hidden email]> wrote:

> Hi all,
>
>> and which VM do you use (there is a System report browser where you can
>> find the information.
>
> I've somehow managed to get the information from System report browser:
>
> Image
> -----
> /home/demi/mess/2017/06/tmp2/Pharo.image
> Pharo5.0
> Latest update: #50768
> Unnamed
>
> Virtual Machine
> ---------------
> /home/demi/mess/2017/06/tmp2/pharo-vm/pharo
> CoInterpreter VMMaker.oscog-eem.1855 uuid:
> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
> https://github.com/pharo-project/pharo-vm.git Commit:
> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
> Esteban Lorenzano <[hidden email]> Jenkins build #589
>
> Unix built on May 4 2016 11:54:41 Compiler: 4.6.3
> VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit:
> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
> Esteban Lorenzano <[hidden email]> Jenkins build #589
> CoInterpreter VMMaker.oscog-eem.1855 uuid:
> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>
>
> I noticed that there are more items which could be selected (list in the
> left bar, I mean System report browser), but I cannot get more info, because
> pharo crashes each time I try to select all text from the all items. May be
> it would be helpful (and I'll be able to) to get information only from some
> particular item? But then, I need to know which exactly items would be
> helpful.
>
> Also, I'm attaching to this email log file after execution of the Pharo with
> strace:
>
> strace ./pharo-ui Pharo.image > pharo-ui-with-strace.log 2>&1
>
> I hope it could shed more light on the issue.
>
>

Andrey Tykhonov

Re: Segmentation fault while installing Scale

Ben Coman <[hidden email]> writes:

> Are you on 64-bit using 32-bit Pharo?

This is not pure 64-bit system. This is multilib setup. So, I can execute
32-bit and 64-bit programs on the same machine. This is recent system
installation, and Pharo doesn't work well on it. But it did work well on
another Gentoo Linux system with the same multilib support.

> Can you use ldd to check the pharo binary is linking to these 32-bit libraries?
> http://pharo.org/gnu-linux-installation

$ ldd ./pharo-vm/pharo

linux-gate.so.1 (0xf76f6000)
libm.so.6 => /lib32/libm.so.6 (0xf7664000)
libdl.so.2 => /lib32/libdl.so.2 (0xf765f000)
libpthread.so.0 => /lib32/libpthread.so.0 (0xf7643000)
libc.so.6 => /lib32/libc.so.6 (0xf7496000)
/lib/ld-linux.so.2 (0xf76f7000)

This is mostly the same output (except addresses, such as 0xf76f6000, --
I'm writing about this fact just because I'm not sure whether it is
important) which I had seen on the previous Gentoo Linux system.

>
> When you get it working can you provide a recipe for the download page.
>
> Alternatively you might try either (pre-release) 64-bit VM from...
> http://files.pharo.org/vm/pharo-spur64/linux/
> * pharo-linux-x86_64threaded-201702061308-aa78f27.zip
> * pharo-linux-x86_64itimer-201702030802-61970b6.zip

I have tried both with the image downloaded from
http://files.pharo.org/image/60/ (Pharo-Image-6.0-latest.zip).

I get the same result:

$ ./pharo Pharo-60386.image
This interpreter (vers. 68021) cannot read image file (vers. 6521).
Press CR to quit...
zsh: exit 1 ./pharo ../tmp64/Pharo-60386.image

> http://forum.world.st/Unix-heartbeat-thread-vs-itimer-td4928943.html
>
> and just expand the image zip in the same folder...
> http://files.pharo.org/image/60/
> * 60385-64.zip

Thank you!

--
Andriy

>
> cheers -ben
>
> On Sat, Feb 11, 2017 at 5:49 AM, Andrey Tykhonov <[hidden email]> wrote:
>> Hi all,
>>
>>> and which VM do you use (there is a System report browser where you can
>>> find the information.
>>
>> I've somehow managed to get the information from System report browser:
>>
>> Image
>> -----
>> /home/demi/mess/2017/06/tmp2/Pharo.image
>> Pharo5.0
>> Latest update: #50768
>> Unnamed
>>
>> Virtual Machine
>> ---------------
>> /home/demi/mess/2017/06/tmp2/pharo-vm/pharo
>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>> https://github.com/pharo-project/pharo-vm.git Commit:
>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>>
>> Unix built on May 4 2016 11:54:41 Compiler: 4.6.3
>> VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit:
>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>
>>
>> I noticed that there are more items which could be selected (list in the
>> left bar, I mean System report browser), but I cannot get more info, because
>> pharo crashes each time I try to select all text from the all items. May be
>> it would be helpful (and I'll be able to) to get information only from some
>> particular item? But then, I need to know which exactly items would be
>> helpful.
>>
>> Also, I'm attaching to this email log file after execution of the Pharo with
>> strace:
>>
>> strace ./pharo-ui Pharo.image > pharo-ui-with-strace.log 2>&1
>>
>> I hope it could shed more light on the issue.
>>
>>

Andrey Tykhonov

Re: Segmentation fault while installing Scale

In reply to this post by Andrey Tykhonov

Hi all,

I've managed to get all information from the System report

browser. I'll attach it to this email. Surprisingly (at least for me),

Pharo doesn't crash if I execute it like the following:

strace -f ./pharo-ui Pharo.image

(before this, I executed it without -f). So, I'm attaching also part

of the output from the command execution. strace generates a lot of

such log messages like you can see in the log file strace-f-pharo.log

(something is wrong, but I'm not sure what exactly is wrong).

Best regards,

Andriy.

system-browser-report.log (39K) Download Attachment

strace-f-pharo.log (4K) Download Attachment

Ben Coman

Re: Segmentation fault while installing Scale

In reply to this post by Andrey Tykhonov

On Sun, Feb 12, 2017 at 5:18 AM, Andriy Tykhonov <[hidden email]> wrote:

> Ben Coman <[hidden email]> writes:
>
>> Are you on 64-bit using 32-bit Pharo?
>
> This is not pure 64-bit system. This is multilib setup. So, I can execute
> 32-bit and 64-bit programs on the same machine. This is recent system
> installation, and Pharo doesn't work well on it. But it did work well on
> another Gentoo Linux system with the same multilib support.
>
>> Can you use ldd to check the pharo binary is linking to these 32-bit libraries?
>> http://pharo.org/gnu-linux-installation
>
> $ ldd ./pharo-vm/pharo
>
> linux-gate.so.1 (0xf76f6000)
> libm.so.6 => /lib32/libm.so.6 (0xf7664000)
> libdl.so.2 => /lib32/libdl.so.2 (0xf765f000)
> libpthread.so.0 => /lib32/libpthread.so.0 (0xf7643000)
> libc.so.6 => /lib32/libc.so.6 (0xf7496000)
> /lib/ld-linux.so.2 (0xf76f7000)

Okay, so four out of six are obviously bound to 32bit libs.

linux-gate seems okay per...
http://man7.org/linux/man-pages/man7/vdso.7.html
Note that the vDSO that is used is based on the ABI of your user-
space code and not the ABI of the kernel. Thus, for example, when
you run an i386 32-bit ELF binary, you'll get the same vDSO
regardless of whether you run it under an i386 32-bit kernel or under
an x86_64 64-bit kerne l.

Could you check if ld-linux symlinks to 32-bit location?

>
> This is mostly the same output (except addresses, such as 0xf76f6000, --
> I'm writing about this fact just because I'm not sure whether it is
> important) which I had seen on the previous Gentoo Linux system.
>
>>
>> When you get it working can you provide a recipe for the download page.
>>
>> Alternatively you might try either (pre-release) 64-bit VM from...
>> http://files.pharo.org/vm/pharo-spur64/linux/
>> * pharo-linux-x86_64threaded-201702061308-aa78f27.zip
>> * pharo-linux-x86_64itimer-201702030802-61970b6.zip
>
> I have tried both with the image downloaded from
> http://files.pharo.org/image/60/ (Pharo-Image-6.0-latest.zip).
>
> I get the same result:
>
> $ ./pharo Pharo-60386.image
> This interpreter (vers. 68021) cannot read image file (vers. 6521).
> Press CR to quit...
> zsh: exit 1 ./pharo ../tmp64/Pharo-60386.image

I'm not completely sure, but I think this indicates you're using
a 64-bit VM (68021) to open a 32-bit Image (6531).
IIUC you need to use Pharo64-60386.image from this zip...

However I guess Scale needs FFI and I'm not sure
of 64 bit FFI status on Linux. (Esteban?)

>> http://files.pharo.org/image/60/
>> * 60385-64.zip

>> On Sat, Feb 11, 2017 at 5:49 AM, Andrey Tykhonov <[hidden email]> wrote:
>>> Hi all,
>>>
>>>> and which VM do you use (there is a System report browser where you can
>>>> find the information.
>>>
>>> I've somehow managed to get the information from System report browser:
>>>
>>> Image
>>> -----
>>> /home/demi/mess/2017/06/tmp2/Pharo.image
>>> Pharo5.0
>>> Latest update: #50768
>>> Unnamed
>>>
>>> Virtual Machine
>>> ---------------
>>> /home/demi/mess/2017/06/tmp2/pharo-vm/pharo
>>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>> https://github.com/pharo-project/pharo-vm.git Commit:
>>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>>>
>>> Unix built on May 4 2016 11:54:41 Compiler: 4.6.3
>>> VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit:
>>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>
>>>
>>> I noticed that there are more items which could be selected (list in the
>>> left bar, I mean System report browser), but I cannot get more info, because
>>> pharo crashes each time I try to select all text from the all items. May be
>>> it would be helpful (and I'll be able to) to get information only from some
>>> particular item? But then, I need to know which exactly items would be
>>> helpful.
>>>
>>> Also, I'm attaching to this email log file after execution of the Pharo with
>>> strace:
>>>
>>> strace ./pharo-ui Pharo.image > pharo-ui-with-strace.log 2>&1
>>>
>>> I hope it could shed more light on the issue.
>>>
>>>
>

Sven Van Caekenberghe-2

Re: Segmentation fault while installing Scale

Note that he managed to run the System Report UI, which means his image was running pretty normally at some point ...

> On 12 Feb 2017, at 10:26, Ben Coman <[hidden email]> wrote:
>
> On Sun, Feb 12, 2017 at 5:18 AM, Andriy Tykhonov <[hidden email]> wrote:
>> Ben Coman <[hidden email]> writes:
>>
>>> Are you on 64-bit using 32-bit Pharo?
>>
>> This is not pure 64-bit system. This is multilib setup. So, I can execute
>> 32-bit and 64-bit programs on the same machine. This is recent system
>> installation, and Pharo doesn't work well on it. But it did work well on
>> another Gentoo Linux system with the same multilib support.
>>
>>> Can you use ldd to check the pharo binary is linking to these 32-bit libraries?
>>> http://pharo.org/gnu-linux-installation
>>
>> $ ldd ./pharo-vm/pharo
>>
>> linux-gate.so.1 (0xf76f6000)
>> libm.so.6 => /lib32/libm.so.6 (0xf7664000)
>> libdl.so.2 => /lib32/libdl.so.2 (0xf765f000)
>> libpthread.so.0 => /lib32/libpthread.so.0 (0xf7643000)
>> libc.so.6 => /lib32/libc.so.6 (0xf7496000)
>> /lib/ld-linux.so.2 (0xf76f7000)
>
> Okay, so four out of six are obviously bound to 32bit libs.
>
> linux-gate seems okay per...
> http://man7.org/linux/man-pages/man7/vdso.7.html
> Note that the vDSO that is used is based on the ABI of your user-
> space code and not the ABI of the kernel. Thus, for example, when
> you run an i386 32-bit ELF binary, you'll get the same vDSO
> regardless of whether you run it under an i386 32-bit kernel or under
> an x86_64 64-bit kerne l.
>
> Could you check if ld-linux symlinks to 32-bit location?
>
>>
>> This is mostly the same output (except addresses, such as 0xf76f6000, --
>> I'm writing about this fact just because I'm not sure whether it is
>> important) which I had seen on the previous Gentoo Linux system.
>>
>>>
>>> When you get it working can you provide a recipe for the download page.
>>>
>>> Alternatively you might try either (pre-release) 64-bit VM from...
>>> http://files.pharo.org/vm/pharo-spur64/linux/
>>> * pharo-linux-x86_64threaded-201702061308-aa78f27.zip
>>> * pharo-linux-x86_64itimer-201702030802-61970b6.zip
>>
>> I have tried both with the image downloaded from
>> http://files.pharo.org/image/60/ (Pharo-Image-6.0-latest.zip).
>>
>> I get the same result:
>>
>> $ ./pharo Pharo-60386.image
>> This interpreter (vers. 68021) cannot read image file (vers. 6521).
>> Press CR to quit...
>> zsh: exit 1 ./pharo ../tmp64/Pharo-60386.image
>
> I'm not completely sure, but I think this indicates you're using
> a 64-bit VM (68021) to open a 32-bit Image (6531).
> IIUC you need to use Pharo64-60386.image from this zip...
>
> However I guess Scale needs FFI and I'm not sure
> of 64 bit FFI status on Linux. (Esteban?)
>
>>> http://files.pharo.org/image/60/
>>> * 60385-64.zip
>
>
>>> On Sat, Feb 11, 2017 at 5:49 AM, Andrey Tykhonov <[hidden email]> wrote:
>>>> Hi all,
>>>>
>>>>> and which VM do you use (there is a System report browser where you can
>>>>> find the information.
>>>>
>>>> I've somehow managed to get the information from System report browser:
>>>>
>>>> Image
>>>> -----
>>>> /home/demi/mess/2017/06/tmp2/Pharo.image
>>>> Pharo5.0
>>>> Latest update: #50768
>>>> Unnamed
>>>>
>>>> Virtual Machine
>>>> ---------------
>>>> /home/demi/mess/2017/06/tmp2/pharo-vm/pharo
>>>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>> https://github.com/pharo-project/pharo-vm.git Commit:
>>>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>>>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>>>>
>>>> Unix built on May 4 2016 11:54:41 Compiler: 4.6.3
>>>> VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit:
>>>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>>>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>>>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>>
>>>>
>>>> I noticed that there are more items which could be selected (list in the
>>>> left bar, I mean System report browser), but I cannot get more info, because
>>>> pharo crashes each time I try to select all text from the all items. May be
>>>> it would be helpful (and I'll be able to) to get information only from some
>>>> particular item? But then, I need to know which exactly items would be
>>>> helpful.
>>>>
>>>> Also, I'm attaching to this email log file after execution of the Pharo with
>>>> strace:
>>>>
>>>> strace ./pharo-ui Pharo.image > pharo-ui-with-strace.log 2>&1
>>>>
>>>> I hope it could shed more light on the issue.

Guillermo Polito

Re: Segmentation fault while installing Scale

Maybe it's something to do with his gentoo's version of some library? libc? It looks like it's some problem of Pharo in gentoo, not necessarily scale.

On Sun, Feb 12, 2017 at 11:05 AM, Sven Van Caekenberghe <[hidden email]> wrote:

Note that he managed to run the System Report UI, which means his image was running pretty normally at some point ...

> On 12 Feb 2017, at 10:26, Ben Coman <[hidden email]> wrote:
>
> On Sun, Feb 12, 2017 at 5:18 AM, Andriy Tykhonov <[hidden email]> wrote:
>> Ben Coman <[hidden email]> writes:
>>
>>> Are you on 64-bit using 32-bit Pharo?
>>
>> This is not pure 64-bit system. This is multilib setup. So, I can execute
>> 32-bit and 64-bit programs on the same machine. This is recent system
>> installation, and Pharo doesn't work well on it. But it did work well on
>> another Gentoo Linux system with the same multilib support.
>>
>>> Can you use ldd to check the pharo binary is linking to these 32-bit libraries?
>>> http://pharo.org/gnu-linux-installation
>>
>> $ ldd ./pharo-vm/pharo
>>
>> linux-gate.so.1 (0xf76f6000)
>> libm.so.6 => /lib32/libm.so.6 (0xf7664000)
>> libdl.so.2 => /lib32/libdl.so.2 (0xf765f000)
>> libpthread.so.0 => /lib32/libpthread.so.0 (0xf7643000)
>> libc.so.6 => /lib32/libc.so.6 (0xf7496000)
>> /lib/ld-linux.so.2 (0xf76f7000)
>
> Okay, so four out of six are obviously bound to 32bit libs.
>
> linux-gate seems okay per...
> http://man7.org/linux/man-pages/man7/vdso.7.html
> Note that the vDSO that is used is based on the ABI of your user-
> space code and not the ABI of the kernel. Thus, for example, when
> you run an i386 32-bit ELF binary, you'll get the same vDSO
> regardless of whether you run it under an i386 32-bit kernel or under
> an x86_64 64-bit kerne l.
>
> Could you check if ld-linux symlinks to 32-bit location?
>
>>
>> This is mostly the same output (except addresses, such as 0xf76f6000, --
>> I'm writing about this fact just because I'm not sure whether it is
>> important) which I had seen on the previous Gentoo Linux system.
>>
>>>
>>> When you get it working can you provide a recipe for the download page.
>>>
>>> Alternatively you might try either (pre-release) 64-bit VM from...
>>> http://files.pharo.org/vm/pharo-spur64/linux/
>>> * pharo-linux-x86_64threaded-201702061308-aa78f27.zip
>>> * pharo-linux-x86_64itimer-201702030802-61970b6.zip
>>
>> I have tried both with the image downloaded from
>> http://files.pharo.org/image/60/ (Pharo-Image-6.0-latest.zip).
>>
>> I get the same result:
>>
>> $ ./pharo Pharo-60386.image
>> This interpreter (vers. 68021) cannot read image file (vers. 6521).
>> Press CR to quit...
>> zsh: exit 1 ./pharo ../tmp64/Pharo-60386.image
>
> I'm not completely sure, but I think this indicates you're using
> a 64-bit VM (68021) to open a 32-bit Image (6531).
> IIUC you need to use Pharo64-60386.image from this zip...
>
> However I guess Scale needs FFI and I'm not sure
> of 64 bit FFI status on Linux. (Esteban?)
>
>>> http://files.pharo.org/image/60/
>>> * 60385-64.zip
>
>
>>> On Sat, Feb 11, 2017 at 5:49 AM, Andrey Tykhonov <[hidden email]> wrote:
>>>> Hi all,
>>>>
>>>>> and which VM do you use (there is a System report browser where you can
>>>>> find the information.
>>>>
>>>> I've somehow managed to get the information from System report browser:
>>>>
>>>> Image
>>>> -----
>>>> /home/demi/mess/2017/06/tmp2/Pharo.image
>>>> Pharo5.0
>>>> Latest update: #50768
>>>> Unnamed
>>>>
>>>> Virtual Machine
>>>> ---------------
>>>> /home/demi/mess/2017/06/tmp2/pharo-vm/pharo
>>>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>> https://github.com/pharo-project/pharo-vm.git Commit:
>>>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>>>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>>>>
>>>> Unix built on May 4 2016 11:54:41 Compiler: 4.6.3
>>>> VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit:
>>>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By:
>>>> Esteban Lorenzano <[hidden email]> Jenkins build #589
>>>> CoInterpreter VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid:
>>>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016
>>>>
>>>>
>>>> I noticed that there are more items which could be selected (list in the
>>>> left bar, I mean System report browser), but I cannot get more info, because
>>>> pharo crashes each time I try to select all text from the all items. May be
>>>> it would be helpful (and I'll be able to) to get information only from some
>>>> particular item? But then, I need to know which exactly items would be
>>>> helpful.
>>>>
>>>> Also, I'm attaching to this email log file after execution of the Pharo with
>>>> strace:
>>>>
>>>> strace ./pharo-ui Pharo.image > pharo-ui-with-strace.log 2>&1
>>>>
>>>> I hope it could shed more light on the issue.