- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Segmentation fault while installing Scale

by Guillermo Polito

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 <bera.clement(a)gmail.com> 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 <stepharo.self(a)gmail.com> > 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 <atykhonov(a)gmail.com> >> wrote: >> >>> Hi all! >>> >>> While executing the following command: >>> >>> $ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setup >>> Scale.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 >>> >>> >>> >> >

Feb. 7, 2017

Re: [Pharo-dev] [QA] Debugger buttons explained

by Thierry Goubier

Hi Hilaire, I find your use case interesting. It used to be the case, that one could discover an application commands by exploring the objects making up the GUI... Now, with Spec or Glamour, is that still the case? It seems not any more. Doru, can you confirm? Regards, Thierry 2017-02-06 21:48 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: > Ok, give a look to SpecDebugActionButton, this class has no user, only > progma reference, not easy to track the logic. > > Never mind I test on a halt in its #update method. Nothing happen when > opening the debugger. May be there is instance in memory, no idea under > which name it is referenced, may be not. > > Inspecting the debugger window does not help, it is a kind of generic > morph. > > Never mind, can try to look at the menu item "Debug it" in the > playground window, I used to find the action there. Oops, get lost > there, I see #debugSelection looks promising, see announcement. Get lost > again. > > No idea, someone else should put these tooltips in the appropriate place. > > > > Le 06/02/2017 Ã 21:14, Hilaire a Ã©crit : > > No user of actionType, but I guess user or pragma, how do you guys track > > the logic from here > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 7, 2017

Re: [Pharo-dev] Pharo 60 need help white-theme-color-for-button-is-not-good

by denker

> On 7 Feb 2017, at 08:07, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > No it is important. > There is no point to have a supercool system that looks so bad and turn people off. > But I do not get it your 13136 was integrated. > > No, this is exactly an example of this âeven the tiniest most obvious thing needs workâ. The slice was done for an older version, nobody cared to update it for the current development version, in the end the issue was closed as *nobody* cared to put 5 minutes inâ¦ There is no magic. "This issue is about Pharo3, with Pharo4 already released and Pharo5 under development, the changes can not be merged due to too many changes in the touched code. Please check Pharo5 and, if this change is still needed, resubmit a new slice. I will close this issue as "Stale (timeout)â.â Marcus

Feb. 7, 2017

Re: [Pharo-dev] Segmentation fault while installing Scale

by ClÃ©ment Bera

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 <stepharo.self(a)gmail.com> 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 <atykhonov(a)gmail.com> > wrote: > >> Hi all! >> >> While executing the following command: >> >> $ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setup >> Scale.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 >> >> >> >

Feb. 7, 2017

Re: [Pharo-dev] [QA] Debugger buttons explained

by Sven Van Caekenberghe

> On 7 Feb 2017, at 08:05, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Sven I do not get > > Step over the highlighted message, i.e. do not follow the sent message, taking debugger control after the method invoked returns or whenever execution should return inside a block used as an argument before that. > > in particular the taking debugger control > may be > > give back debugger control? Give back might be clearer than take back, I guess, I don't know. Maybe the 'before that' should be moved too, as in Step over the highlighted message, i.e. do not follow the sent message, give back debugger control after the method invoked returns or whenever before that execution should return inside a block used as an argument. > On Mon, Feb 6, 2017 at 7:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 6 Feb 2017, at 18:55, Hilaire <hilaire(a)drgeo.eu> wrote: > > > > How will you describe these buttons in the debugger? > > Here are proposals for tooltips, please fix it, I am sure there are > > better way to write it. > > > > Proceed > > Quit the debugger and resume the execution of the method. > > > > Restart > > Reset the local variable and restart stepping at the beginning of the > > method. > > > > Into > > Step in the highlighted message, i.e. follow the sent message in its method. > > > > Over > > Execute the highlighted message, i.e. do not follow the sent message in > > its method. > > > > Through > > Execute the highlighted message, when argument is a bloc to #do:, > > #collect:, #select: #detect: step in the bloc. > > That last one is not correct. It has nothing to do with specific iteration selectors. It means: stop when execution returns in one of the argument blocks. It also works for #on:error: #streamContents: or any other message that accepts blocks as argument - which is pretty cool. > > Consult DebugSession for good descriptions of the actions. > > > This is my version/take, probably not perfect either. > > > Into > > Step in the highlighted message, i.e. follow the sent message, taking debugger control in the method invoked. > > Over > > Step over the highlighted message, i.e. do not follow the sent message, taking debugger control after the method invoked returns. > > Through > > Step over the highlighted message, i.e. do not follow the sent message, taking debugger control after the method invoked returns or whenever execution should return inside a block used as an argument before that. > > Restart > > Go back the start of the current execution context, resetting all local variables and take debugger control. > > Continue > > Relinquish debugger control and proceed execution from the current point of debugger control. > > > > https://pharo.fogbugz.com/f/cases/19654/Tooltips-with-description-of-the-ov… > > > > -- > > Dr. Geo > > http://drgeo.eu > > > > > > >

Feb. 7, 2017

Re: [Pharo-dev] Pharo 60 need help white-theme-color-for-button-is-not-good

by Stephane Ducasse

No it is important. There is no point to have a supercool system that looks so bad and turn people off. But I do not get it your 13136 was integrated. On Mon, Feb 6, 2017 at 6:28 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > I proposed that a while ago because these gradients are bad looking > (especially in an age of flat design). > > https://pharo.fogbugz.com/f/cases/13132/Ugly-gradients-in- > Pharo3Theme-Not-in-line-with-the-times > > Same for those ugly flat scrollbars. > > https://pharo.fogbugz.com/f/cases/13136/Pharo3Theme- > scrollbars-looking-like-dead-without-visual-indicators > > This one has a slice. > > Maybe Pharo 6 is not too late for those slices. > > Phil > > > > On Mon, Feb 6, 2017 at 5:59 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> https://pharo.fogbugz.com/f/cases/19657/white-theme-color-fo >> r-button-is-not-good >> >> If we compare the selection color for the dark theme, the blue is >> stronger and much better to see. >> This is particularly true for class/instance side button, >> >> I would be good to have a better white theme with stronger selection >> colors. >> > >

Feb. 7, 2017

Re: [Pharo-dev] [QA] Debugger buttons explained

by Stephane Ducasse

Sven I do not get Step over the highlighted message, i.e. do not follow the sent message, taking debugger control after the method invoked returns or whenever execution should return inside a block used as an argument before that. in particular the taking debugger control may be give back debugger control? On Mon, Feb 6, 2017 at 7:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 6 Feb 2017, at 18:55, Hilaire <hilaire(a)drgeo.eu> wrote: > > > > How will you describe these buttons in the debugger? > > Here are proposals for tooltips, please fix it, I am sure there are > > better way to write it. > > > > Proceed > > Quit the debugger and resume the execution of the method. > > > > Restart > > Reset the local variable and restart stepping at the beginning of the > > method. > > > > Into > > Step in the highlighted message, i.e. follow the sent message in its > method. > > > > Over > > Execute the highlighted message, i.e. do not follow the sent message in > > its method. > > > > Through > > Execute the highlighted message, when argument is a bloc to #do:, > > #collect:, #select: #detect: step in the bloc. > > That last one is not correct. It has nothing to do with specific iteration > selectors. It means: stop when execution returns in one of the argument > blocks. It also works for #on:error: #streamContents: or any other message > that accepts blocks as argument - which is pretty cool. > > Consult DebugSession for good descriptions of the actions. > > > This is my version/take, probably not perfect either. > > > Into > > Step in the highlighted message, i.e. follow the sent message, taking > debugger control in the method invoked. > > Over > > Step over the highlighted message, i.e. do not follow the sent message, > taking debugger control after the method invoked returns. > > Through > > Step over the highlighted message, i.e. do not follow the sent message, > taking debugger control after the method invoked returns or whenever > execution should return inside a block used as an argument before that. > > Restart > > Go back the start of the current execution context, resetting all local > variables and take debugger control. > > Continue > > Relinquish debugger control and proceed execution from the current point > of debugger control. > > > > https://pharo.fogbugz.com/f/cases/19654/Tooltips-with- > description-of-the-over-and-through-debugger-buttons-actions > > > > -- > > Dr. Geo > > http://drgeo.eu > > > > > > >

Feb. 7, 2017

Re: [Pharo-dev] Debugger hang when step throught

by Stephane Ducasse

tx for the report hilaire. Indeed I can reproduce your bug - I pasted it - I did debug it over over and through trhough and my system froze. On Mon, Feb 6, 2017 at 7:04 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hello, > > The faulty code bellow when debugged and 'step through' cause the > debugger to hang: > > self inform: '1'. > #(2 3 4) select: [:i| i] thenDo: [:n| self inform: n printString ]. > self inform: '5'. > > It seems trapped in an infinite loop, you can more or less get control > back with Alt+[.] > > > When step in, the debugger properly report the error. > > Pharo #60362. > > > I did not see similar bug report, shall I? > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 7, 2017

Re: [Pharo-dev] Segmentation fault while installing Scale

by Stephane Ducasse

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 <atykhonov(a)gmail.com> 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 > > >

Feb. 7, 2017

Re: [Pharo-dev] Pharo 6 update catalog entries

by Dimitris Chloupis

Fair point, I will make the changes. Glad you find it useful, is there any new feature you want ? On Mon, 6 Feb 2017 at 18:05, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > kilon.alios wrote > > I see little reason to support individual pharo versions because I focus > > always on the latest version. > > I'm not suggesting that you maintain compatibility ongoingly with various > versions, but if you mark compatible versions as such in the catalog, users > won't get an unnecessary warning. Either way, thanks for the tool! I > happily > use it daily :) > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Pharo-6-update-catalog-entries-tp4932354p4933169.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Feb. 7, 2017