Re: [Pharo-users] Meta-clicking to bring up the halo

[Stephane Ducasse]

Hi

Normally bringing the halo is done using Shift+command(on mac)+alt.
Now in Pharo there is also a Platform class and I do not know if the
keybinding dispatch to it.
So this is not clear that this is a vm things. With the introduction of
SDL20 we want to manage all the
event interpretation at the image level.
Right now the VM is doing too much and badly
- we handled touch events via OSWindow (SDL inside)
- in the VM there is no way to know if some keys have been pressed.

Moving all the logic to the image with make the vm slimmer and focused more
on its key job.
We should continue to integrate more SDL20.

Stef


On Sun, May 14, 2017 at 1:14 AM, horrido  wrote:

> I have Pharo 5.0 running under both Windows 7 and Raspbian (using the Spur
> VM). Curiously, I can bring up the halo in Windows by meta-clicking, but
> not
> so in Raspbian. In Raspbian, the only thing I can do is 'add halo' from a
> context menu (which I can also do in Windows).
>
> I'm just guessing but this issue must be related to the VM, since the Pharo
> 5.0 image *should* be the same on both platforms (?).
>
>
>
> --
> View this message in context: http://forum.world.st/Meta-
> clicking-to-bring-up-the-halo-tp4947067.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

[Stephane Ducasse]

I do not really see why loading a package would be related to old glibc but
may be :)
With software who knows.
Now what is important for you is that you always tries to load and produce
configurations.

Stef

On Sun, May 14, 2017 at 2:03 AM, Andreas Sunardi 
wrote:

>  Hi Stephane,
>
> I shall read that Metacello chapter. I had considered this case closed
> until you replied again. I took another peek and I think I found the root
> cause. And for the sake of those who stumble on this email thread, I should
> clarify this.
>
> This is probably related to my old email thread about running Pharo 5.0 on
> linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download to
> work properly.
> http://lists.pharo.org/pipermail/pharo-users_lists.
> pharo.org/2016-October/028431.html
>
> Following your solution, after installing PetitParser from Catalog Browser
> in Windows version, I noticed the ConfigurationOfPetitParser version is
> TudorGirba.80, the version I had problem in linux. I then wondered why it
> didn't work on my linux with old glibc versions. Here's what I found
>
> Download and version (SystemVersion current imageVersionString):
> centos  Pharo-5.0-50761-
> linux Pharo-5.0-50772-
> linux-oldLibC *Pharo-6.0-60257-*
>
> Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use
> where PetitParser installation failed.
>
> Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load
> and #loadDevelopment versions, PetitParser installation works fine for
> images that come from linux and centos  versions, but not from
> linux-oldLibC.
>
> So, I believe that is the problem. I'm not sure what's the right solution,
> but I think I can stay in this image and use TudorGirba.77 version or I can
> try using image from linux version.
>
> Thanks again. If you hadn't replied about Metacello, I'd have never taken
> another look and found this.
>
> --
> Andreas Sunardi
>
> On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse <
> stepharo.s...@gmail.com> wrote:
>
>> You should read the beginning of the chapter on metacello.
>> Metacello is a map
>> Monticello element of the map
>>
>> You load elements by asking the map.
>>
>> Stef
>>
>> On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi 
>> wrote:
>>
>>> Hi Stephane,
>>>
>>> Indeed, PetitParser installation from Catalog Browser works just fine!
>>> Thank you very much.
>>>
>>> I used Monticello Browser before, but not Catalog Browser. I didn't know
>>> this is the preferred method to install package. I don't think
>>> DeepIntoPharo mentions about Catalog Browser, but maybe my version is
>>> outdated.
>>>
>>> Thanks again, Stephane.
>>>
>>> --
>>> Andreas Sunardi
>>>
>>> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse <
>>> stepharo.s...@gmail.com> wrote:
>>>
 Sorry I meant the catalogBrowser.
 Using the catalogBrowser on a given version of Pharo you should access
 the configuration for this version (if people updated it correctly).
 Our plan is to make sure that such configurations are validated.
 Stef

 On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse <
 stepharo.s...@gmail.com> wrote:

> Hi andreas
>
> Normally you should be able to load a package using the
> ConfigurationBrowser and the configuration (now I do not know the one of
> PetitParser)
> should take care of the pharo version for you.
>
> stef
>
>
> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi 
> wrote:
>
>> Following DeepIntoPharo, I tried to install PetitParser into my Pharo
>> 5.0 image (I noticed PetitParser installation problem email in March). It
>> failed with the message WinPlatform class was undefined. I went to 
>> Moose's
>> PetitParser site in smalltalkhub and followed the instruction there, and
>> this also failed.
>>
>> Out of frustration, I downloaded Moose 6.0 and thought I'd start from
>> Moose image instead. But then I noticed Moose's PetitParser package has
>> ConfigurationOfPetitParser from version TudorGirba.77 and the 
>> instruction I
>> followed was trying to install it using version TudorGirba.80. Back to my
>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load 
>> version
>> TudorGirba.77. And this works!
>>
>> But this way to solve PetitParser installation problem seems wrong. I
>> figure if this could very well happen with other packages too. What is 
>> the
>> right way to find package version that works with my image/pharo version?
>> Or is this an issue with PetitParser package itself and should I 
>> ask/report
>> this to Moose team?
>>
>> --
>> Andreas Sunardi
>>
>
>

>>>
>>
>

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

[Ben Coman]

On Sun, May 14, 2017 at 8:03 AM, Andreas Sunardi  wrote:
>  Hi Stephane,
>
> I shall read that Metacello chapter. I had considered this case closed until
> you replied again. I took another peek and I think I found the root cause.
> And for the sake of those who stumble on this email thread, I should clarify
> this.
>
> This is probably related to my old email thread about running Pharo 5.0 on
> linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download to
> work properly.
> http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2016-October/028431.html
>
> Following your solution, after installing PetitParser from Catalog Browser
> in Windows version, I noticed the ConfigurationOfPetitParser version is
> TudorGirba.80, the version I had problem in linux. I then wondered why it
> didn't work on my linux with old glibc versions. Here's what I found
>
> Download and version (SystemVersion current imageVersionString):
> centos  Pharo-5.0-50761-
> linux Pharo-5.0-50772-
> linux-oldLibC *Pharo-6.0-60257-*

Can you provide the links for those downloads?

cheers -ben

>
> Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use where
> PetitParser installation failed.
>
> Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load and
> #loadDevelopment versions, PetitParser installation works fine for images
> that come from linux and centos  versions, but not from linux-oldLibC.
>
> So, I believe that is the problem. I'm not sure what's the right solution,
> but I think I can stay in this image and use TudorGirba.77 version or I can
> try using image from linux version.
>
> Thanks again. If you hadn't replied about Metacello, I'd have never taken
> another look and found this.
>
> --
> Andreas Sunardi
>
> On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse 
> wrote:
>>
>> You should read the beginning of the chapter on metacello.
>> Metacello is a map
>> Monticello element of the map
>>
>> You load elements by asking the map.
>>
>> Stef
>>
>> On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi 
>> wrote:
>>>
>>> Hi Stephane,
>>>
>>> Indeed, PetitParser installation from Catalog Browser works just fine!
>>> Thank you very much.
>>>
>>> I used Monticello Browser before, but not Catalog Browser. I didn't know
>>> this is the preferred method to install package. I don't think DeepIntoPharo
>>> mentions about Catalog Browser, but maybe my version is outdated.
>>>
>>> Thanks again, Stephane.
>>>
>>> --
>>> Andreas Sunardi
>>>
>>> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse
>>>  wrote:

 Sorry I meant the catalogBrowser.
 Using the catalogBrowser on a given version of Pharo you should access
 the configuration for this version (if people updated it correctly).
 Our plan is to make sure that such configurations are validated.
 Stef

 On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse
  wrote:
>
> Hi andreas
>
> Normally you should be able to load a package using the
> ConfigurationBrowser and the configuration (now I do not know the one of
> PetitParser)
> should take care of the pharo version for you.
>
> stef
>
>
> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi 
> wrote:
>>
>> Following DeepIntoPharo, I tried to install PetitParser into my Pharo
>> 5.0 image (I noticed PetitParser installation problem email in March). It
>> failed with the message WinPlatform class was undefined. I went to 
>> Moose's
>> PetitParser site in smalltalkhub and followed the instruction there, and
>> this also failed.
>>
>> Out of frustration, I downloaded Moose 6.0 and thought I'd start from
>> Moose image instead. But then I noticed Moose's PetitParser package has
>> ConfigurationOfPetitParser from version TudorGirba.77 and the 
>> instruction I
>> followed was trying to install it using version TudorGirba.80. Back to my
>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load 
>> version
>> TudorGirba.77. And this works!
>>
>> But this way to solve PetitParser installation problem seems wrong. I
>> figure if this could very well happen with other packages too. What is 
>> the
>> right way to find package version that works with my image/pharo 
>> version? Or
>> is this an issue with PetitParser package itself and should I ask/report
>> this to Moose team?
>>
>> --
>> Andreas Sunardi
>
>

>>>
>>
>

Re: [Pharo-users] A Logo Proposal for Smalltalk

[horrido]

Sven Van Caekenberghe-2 wrote
> I think a stylised balloon is not bad, it just has to be less complex,
> more logo like, more abstract.

I've taken your comment to heart and I believe I've come up with the ideal
logo:

 

Beautifully abstract. Nice and simple.

And it harkens back to the very famous BYTE 1981 cover *without tying
Smalltalk to the past*. The hot air balloon motif for Smalltalk is
universally recognized, and we cannot ignore it.



--
View this message in context: 
http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4947093.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

[Andreas Sunardi]

Hi Ben,

It's the linux download page from Pharo website
http://pharo.org/gnu-linux-installation


--
Andreas

On Sun, May 14, 2017 at 5:20 AM, Ben Coman  wrote:

> On Sun, May 14, 2017 at 8:03 AM, Andreas Sunardi 
> wrote:
> >  Hi Stephane,
> >
> > I shall read that Metacello chapter. I had considered this case closed
> until
> > you replied again. I took another peek and I think I found the root
> cause.
> > And for the sake of those who stumble on this email thread, I should
> clarify
> > this.
> >
> > This is probably related to my old email thread about running Pharo 5.0
> on
> > linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download
> to
> > work properly.
> > http://lists.pharo.org/pipermail/pharo-users_lists.
> pharo.org/2016-October/028431.html
> >
> > Following your solution, after installing PetitParser from Catalog
> Browser
> > in Windows version, I noticed the ConfigurationOfPetitParser version is
> > TudorGirba.80, the version I had problem in linux. I then wondered why it
> > didn't work on my linux with old glibc versions. Here's what I found
> >
> > Download and version (SystemVersion current imageVersionString):
> > centos  Pharo-5.0-50761-
> > linux Pharo-5.0-50772-
> > linux-oldLibC *Pharo-6.0-60257-*
>
> Can you provide the links for those downloads?
>
> cheers -ben
>
> >
> > Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use
> where
> > PetitParser installation failed.
> >
> > Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load
> and
> > #loadDevelopment versions, PetitParser installation works fine for images
> > that come from linux and centos  versions, but not from linux-oldLibC.
> >
> > So, I believe that is the problem. I'm not sure what's the right
> solution,
> > but I think I can stay in this image and use TudorGirba.77 version or I
> can
> > try using image from linux version.
> >
> > Thanks again. If you hadn't replied about Metacello, I'd have never taken
> > another look and found this.
> >
> > --
> > Andreas Sunardi
> >
> > On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse <
> stepharo.s...@gmail.com>
> > wrote:
> >>
> >> You should read the beginning of the chapter on metacello.
> >> Metacello is a map
> >> Monticello element of the map
> >>
> >> You load elements by asking the map.
> >>
> >> Stef
> >>
> >> On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi 
> >> wrote:
> >>>
> >>> Hi Stephane,
> >>>
> >>> Indeed, PetitParser installation from Catalog Browser works just fine!
> >>> Thank you very much.
> >>>
> >>> I used Monticello Browser before, but not Catalog Browser. I didn't
> know
> >>> this is the preferred method to install package. I don't think
> DeepIntoPharo
> >>> mentions about Catalog Browser, but maybe my version is outdated.
> >>>
> >>> Thanks again, Stephane.
> >>>
> >>> --
> >>> Andreas Sunardi
> >>>
> >>> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse
> >>>  wrote:
> 
>  Sorry I meant the catalogBrowser.
>  Using the catalogBrowser on a given version of Pharo you should access
>  the configuration for this version (if people updated it correctly).
>  Our plan is to make sure that such configurations are validated.
>  Stef
> 
>  On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse
>   wrote:
> >
> > Hi andreas
> >
> > Normally you should be able to load a package using the
> > ConfigurationBrowser and the configuration (now I do not know the
> one of
> > PetitParser)
> > should take care of the pharo version for you.
> >
> > stef
> >
> >
> > On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <
> a.suna...@gmail.com>
> > wrote:
> >>
> >> Following DeepIntoPharo, I tried to install PetitParser into my
> Pharo
> >> 5.0 image (I noticed PetitParser installation problem email in
> March). It
> >> failed with the message WinPlatform class was undefined. I went to
> Moose's
> >> PetitParser site in smalltalkhub and followed the instruction
> there, and
> >> this also failed.
> >>
> >> Out of frustration, I downloaded Moose 6.0 and thought I'd start
> from
> >> Moose image instead. But then I noticed Moose's PetitParser package
> has
> >> ConfigurationOfPetitParser from version TudorGirba.77 and the
> instruction I
> >> followed was trying to install it using version TudorGirba.80. Back
> to my
> >> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load
> version
> >> TudorGirba.77. And this works!
> >>
> >> But this way to solve PetitParser installation problem seems wrong.
> I
> >> figure if this could very well happen with other packages too. What
> is the
> >> right way to find package version that works with my image/pharo
> version? Or
> >> is this an issue with PetitParser package itself and should I
> ask/report
> >> this to Moose team?
> >>
> >> --
> >> Andreas Sunardi
> >
> 

[Pharo-users] Where does inspector store snippets?

[Sean P. DeNigris]

I see the "play-cache" folder but no "inspect-cache". It would be nice to
keep these when rebuilding an image from scratch...



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Where-does-inspector-store-snippets-tp4947096.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

[Pharo-users] New booklet available

[Stephane Ducasse]

A new booklet is joining the collection and it is on Voyage the object to
document mapper developed by E. Lorenzano.

Available in beta http://files.pharo.org/books/ and open to contributors at
https://github.com/SquareBracketAssociates/Booklet-Voyage

Enjoy

Stef

[Pharo-users] Windows equivalent of kill -s SIGUSR1?

[Alistair Grant]

Hi All,

The subject pretty much says it all: Is there an equivalent on Windows
to the linux

kill -s SIGUSR1 

that gets the VM to dump its current status?

Thanks,
Alistair

Re: [Pharo-users] Windows equivalent of kill -s SIGUSR1?

[Henrik Nergaard]

Windows do not have Unix-style signals such as SIGUSR1.

To kill a process you can use Windows PowerShell:

$ Stop-Process -Name Pharo
Or by pid:
$ Get-Process -Name Pharo
$ Stop-Process -Id 42

Best regards,
Henrik

Sent from Mail for Windows 10

From: Alistair Grant
Sent: 14 May 2017 23:18
To: pharo-users@lists.pharo.org
Subject: [Pharo-users] Windows equivalent of kill -s SIGUSR1?

Hi All,

The subject pretty much says it all: Is there an equivalent on Windows
to the linux

kill -s SIGUSR1 

that gets the VM to dump its current status?

Thanks,
Alistair

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

[Andreas Sunardi]

It isn't glibc issue. Perhaps my wording makes it unclear. When I said
'linux' or 'linux with old glibc', I was referring to the image versions
that come with those download options. I wasn't referring to glibc itself.

--
Andreas Sunardi


On Sun, May 14, 2017 at 3:14 AM, Stephane Ducasse 
wrote:

> I do not really see why loading a package would be related to old glibc
> but may be :)
> With software who knows.
> Now what is important for you is that you always tries to load and produce
> configurations.
>
> Stef
>
> On Sun, May 14, 2017 at 2:03 AM, Andreas Sunardi 
> wrote:
>
>>  Hi Stephane,
>>
>> I shall read that Metacello chapter. I had considered this case closed
>> until you replied again. I took another peek and I think I found the root
>> cause. And for the sake of those who stumble on this email thread, I should
>> clarify this.
>>
>> This is probably related to my old email thread about running Pharo 5.0
>> on linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download
>> to work properly.
>> http://lists.pharo.org/pipermail/pharo-users_lists.pharo.
>> org/2016-October/028431.html
>>
>> Following your solution, after installing PetitParser from Catalog
>> Browser in Windows version, I noticed the ConfigurationOfPetitParser
>> version is TudorGirba.80, the version I had problem in linux. I then
>> wondered why it didn't work on my linux with old glibc versions. Here's
>> what I found
>>
>> Download and version (SystemVersion current imageVersionString):
>> centos  Pharo-5.0-50761-
>> linux Pharo-5.0-50772-
>> linux-oldLibC *Pharo-6.0-60257-*
>>
>> Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use
>> where PetitParser installation failed.
>>
>> Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load
>> and #loadDevelopment versions, PetitParser installation works fine for
>> images that come from linux and centos  versions, but not from
>> linux-oldLibC.
>>
>> So, I believe that is the problem. I'm not sure what's the right
>> solution, but I think I can stay in this image and use TudorGirba.77
>> version or I can try using image from linux version.
>>
>> Thanks again. If you hadn't replied about Metacello, I'd have never taken
>> another look and found this.
>>
>> --
>> Andreas Sunardi
>>
>> On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse <
>> stepharo.s...@gmail.com> wrote:
>>
>>> You should read the beginning of the chapter on metacello.
>>> Metacello is a map
>>> Monticello element of the map
>>>
>>> You load elements by asking the map.
>>>
>>> Stef
>>>
>>> On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi 
>>> wrote:
>>>
 Hi Stephane,

 Indeed, PetitParser installation from Catalog Browser works just fine!
 Thank you very much.

 I used Monticello Browser before, but not Catalog Browser. I didn't
 know this is the preferred method to install package. I don't think
 DeepIntoPharo mentions about Catalog Browser, but maybe my version is
 outdated.

 Thanks again, Stephane.

 --
 Andreas Sunardi

 On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse <
 stepharo.s...@gmail.com> wrote:

> Sorry I meant the catalogBrowser.
> Using the catalogBrowser on a given version of Pharo you should access
> the configuration for this version (if people updated it correctly).
> Our plan is to make sure that such configurations are validated.
> Stef
>
> On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse <
> stepharo.s...@gmail.com> wrote:
>
>> Hi andreas
>>
>> Normally you should be able to load a package using the
>> ConfigurationBrowser and the configuration (now I do not know the one of
>> PetitParser)
>> should take care of the pharo version for you.
>>
>> stef
>>
>>
>> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi > > wrote:
>>
>>> Following DeepIntoPharo, I tried to install PetitParser into my
>>> Pharo 5.0 image (I noticed PetitParser installation problem email in
>>> March). It failed with the message WinPlatform class was undefined. I 
>>> went
>>> to Moose's PetitParser site in smalltalkhub and followed the instruction
>>> there, and this also failed.
>>>
>>> Out of frustration, I downloaded Moose 6.0 and thought I'd start
>>> from Moose image instead. But then I noticed Moose's PetitParser package
>>> has ConfigurationOfPetitParser from version TudorGirba.77 and the
>>> instruction I followed was trying to install it using version
>>> TudorGirba.80. Back to my Pharo 5 image, I unload/remove
>>> ConfigurationOfPetitParser and load version TudorGirba.77. And this 
>>> works!
>>>
>>> But this way to solve PetitParser installation problem seems wrong.
>>> I figure if this could very well happen with other packages too. What is
>>> the right way to find package version that works with my ima

Re: [Pharo-users] Windows equivalent of kill -s SIGUSR1?

[Alistair Grant]

Hi Henrik,

On Sun, May 14, 2017 at 09:58:12PM +, Henrik Nergaard wrote:
>  
> Windows do not have Unix-style signals such as SIGUSR1.
> 
> To kill a process you can use Windows PowerShell:
> 
> $ Stop-Process -Name Pharo
> 
> Or by pid:
> 
> $ Get-Process -Name Pharo
> 
> $ Stop-Process -Id 42

Thanks for your reply.

The kill command on Unix is somewhat misnamed, it actually just sends
one of a number of signals to the process.  For some of those signals,
it is up to the process to decide how it will respond.  For the USR1
signal, the VM responds by printing out information about its internal
state, including:

- version information
- C stack backtrace & registers
- All Smalltalk process stacks
- Most recent primitives

What I'm hoping is that the same thing can be done on Windows.

My understanding is that stop-process can only be used for terminating a
process.

Cheers,
Alistair


> From: Alistair Grant
> Sent: 14 May 2017 23:18
> To: pharo-users@lists.pharo.org
> Subject: [Pharo-users] Windows equivalent of kill -s SIGUSR1?
> 
>  
> 
> Hi All,
> 
> The subject pretty much says it all: Is there an equivalent on Windows
> to the linux
> 
> kill -s SIGUSR1 
> 
> that gets the VM to dump its current status?
> 
> Thanks,
> Alistair

Re: [Pharo-users] Windows equivalent of kill -s SIGUSR1?

[K K Subbu]

On Monday 15 May 2017 02:47 AM, Alistair Grant wrote:

The subject pretty much says it all: Is there an equivalent on Windows
to the linux

kill -s SIGUSR1 

that gets the VM to dump its current status?


signals is unix-specific IPC. On Windows, you should be able to "create 
dump file" from right-click menu on Task Manager's process list (if you 
have the perms, of course!).


If you do a lot of system work on windows, sysinternals suite could be 
very useful. It has many utilities for advanced operations (Procdump?) 
on processes and files.


HTH .. Subbu

Re: [Pharo-users] Windows equivalent of kill -s SIGUSR1?

[Alistair Grant]

Hi Subbu,

On Mon, May 15, 2017 at 11:16:45AM +0530, K K Subbu wrote:
> On Monday 15 May 2017 02:47 AM, Alistair Grant wrote:
> >The subject pretty much says it all: Is there an equivalent on Windows
> >to the linux
> >
> >kill -s SIGUSR1 
> >
> >that gets the VM to dump its current status?
> 
> signals is unix-specific IPC. On Windows, you should be able to "create dump
> file" from right-click menu on Task Manager's process list (if you have the
> perms, of course!).
> 
> If you do a lot of system work on windows, sysinternals suite could be very
> useful. It has many utilities for advanced operations (Procdump?) on
> processes and files.

It looks like "dump" was a poor choice of words, as I expanded on in my
reply to Henrik, it's about requesting the VM to print out its internal
information.  The VM continues to function "normally" after the request
has been processed.

Thanks,
Alistair

Re: [Pharo-users] SSL/TLS plugin initailization failed (VM plugin missing ? OS libraries missing ?)

[Julien Delplanque]

Ok, I found a way to fix the problem.

Simply, I needed to install the package lib32-libopenssl-1.0-compat 
which contains
the library with "1.0.0" version. This should be added as dependency to 
the package

in AUR. (the command: # yaourt -S lib32-libopenssl-1.0-compat)

I can help for that if needed. Who manage the pharo-related packages for 
Arch?


Julien


On 09/05/17 11:24, Sven Van Caekenberghe wrote:

For Pharo 5, on the same machine:

$ curl get.pharo.org/50+vm | bash
...

$ ./pharo --version
5.0 #1 Wed May  4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM]
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  Jenkins build #589
Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 
2012 i686 i686 i386 GNU/Linux

$ ./pharo Pharo.image printVersion
[version] 5.0 #50772
$ ./pharo Pharo.image eval "ZnClient new get: 'https://pharo.org'"
4149724864:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert 
handshake failure:s23_clnt.c:769:
ConnectionClosed: Connection closed while waiting for data.
...

This is normal, see 
https://pharo.fogbugz.com/f/cases/19864/Add-support-for-Server-Name-Indication-SNI-to-Zodiac-SSLPlugin
 which is integrated in 6 but not in 5.

Note that the error is different from yours (no linking error, a runtime error).

With other HTTPS sites, it still works on 5:

audio359@audio359:~/pharo-dev/pharo5$ ./pharo Pharo.image eval "ZnClient new get: 
'https://audio359.eu'"
...


On 9 May 2017, at 09:08, Julien Delplanque  wrote:

Hello,

I did the same thing as you and it works.

When I do:

./pharo --version

I get:

5.0-201705022326  Tue May  2 23:46:52 UTC 2017 gcc 4.6.3 [Production Spur ITHB 
VM]
CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 
May  2 2017
StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: 
12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
VM: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: 
Tue May 2 16:26:41 2017 -0700 $
Plugins: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
Linux testing-gce-7a7e75c9-f535-4934-bad2-d5fb6fd60cee 3.13.0-103-generic 
#150~precise1-Ubuntu SMP Thu Nov 24 11:05:34 UTC 2016 i686 i686 i386 GNU/Linux
plugin path: /tmp/pharo/pharo-vm/lib/pharo/5.0-201705022326 [default: 
/tmp/pharo/pharo-vm/lib/pharo/5.0-201705022326/]

And when I check the version of the VM currently installed on my system:

pharo-spur

I get:

5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM]
CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 
16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 
16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
https://github.com/pharo-project/pharo-vm.git Commit: 
9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub 
 Jenkins build #594
Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 
2012 i686 i686 i386 GNU/Linux
plugin path: /usr/share/pharo/spur/ [default: /usr/share/pharo/spur/]

So apparently those are not the same VMs.

Nevertheless, when I open Pharo 6 image that I got using your curl command, it
using the network works with  both VM.

So, I tried to load a Pharo 5 image with the VM:

curl get.pharo.org/50+vm | bash

And when I do:

./pharo Pharo.image eval "ZnClient new get: 'https://pharo.org'"

I get:

ioLoadModule(/tmp/pharo2/pharo-vm/libSqueakSSL.so):
  /usr/lib32/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by 
/tmp/pharo2/pharo-vm/libSqueakSSL.so)
ZdcPluginMissing: SSL/TLS plugin initailization failed (VM plugin missing ? OS 
libraries missing ?)
[ :exception | ZdcPluginMissing signal ] in ZdcPluginSSLSession>>initialize in 
Block: [ :exception | ZdcPluginMissing signal ]
BlockClosure>>cull:
Context>>evaluateSignal:
Context>>handleSignal:
PrimitiveFailed(Exception)>>signal
PrimitiveFailed class(SelectorException class)>>signalFor:
ZdcPluginSSLSession(Object)>>primitiveFailed:
ZdcPluginSSLSession(Object)>>primitiveFailed
ZdcPluginSSLSession>>primitiveSSLCreate
[ handle := self primitiveSSLCreate ] in ZdcPluginSSLSession>>initialize in 
Block: [ handle := self primitiveSSLCreate ]
BlockClosure>>on:do:
ZdcPluginSSLSession>>initialize
ZdcPluginSSLSession class(Behavior)>>new
ZdcSecureSocketStream>>sslSession
ZdcSecureSocketStream>>connect
ZnClient>>setupTLSTo:
ZnClient>>newConnectionTo:
ZnClient>>getConnectionAndExecute
ZnClient>>executeWithRedirectsRemaining:
[ self executeWithRedirectsRemaining: self maxNumberOfRedirects ] in 
ZnClient>>executeWithRetriesRemaining: in Block: [ self 
executeWithRedirectsRemaining: self maxNum