Re: [Pharo-users] fast subclassing/class creation in tests

[Marcus Denker]

Yes… I make a note here and have a look sometimes the next weeks.

e) is really a problem: that both source-storage and change log is the same 
makes things
complex (but of course for the time that it was done the solution is amazingly 
efficient)

Marcus

> On 29 Oct 2015, at 19:14, Peter Uhnák  wrote:
> 
> yes, I already felt that test runs involving unlogged code generation is very 
> slow… can you add an entry on the issue tracker?
> 
> I can, but I am not sure for what. :)
> 
> a) speed up regular class operations (class creation, removal, compilation)
> b) speed up unlogged class ops
> c) modify code generation tests in Pharo (ClassTest, possibly others) to use 
> unlogged/suspendAllWhile
> d) all of the above (as separate issues)
> 
> plus bonus
> e) create classes/methods without polluting the environment (.changes file) 
> (because only removal is unlogged, not creation) (if this is even possible)
> 
> Peter

Re: [Pharo-users] VM crash on Ubuntu 14.04

[Esteban Lorenzano]

not so bad… that actually means that you are running out of heap, badly :P
and since I see a primitiveNativeCall there, most probably your (athens?) 
program is leaking somewhere. 

Esteban

> On 30 Oct 2015, at 18:01, Johan Fabry  wrote:
> 
> 
> More bad luck I’m afraid. What can I do next?
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xb8c0b92d in ?? ()
> (gdb) p (void)printCallStack()
> Cannot access memory at address 0x
> (gdb) 
> 
>> On Oct 30, 2015, at 08:11, Esteban Lorenzano > > wrote:
>> 
>> you can type 
>> 
>> p (void)printCallStack()
>> 
>> then you will have the active stack when crash happened. Is often a lot more 
>> useful than the trace of the vm.
>> 
>> Esteban
>> 
>>> On 29 Oct 2015, at 19:03, Johan Fabry >> > wrote:
>>> 
>>> 
>>> OK, back with access to the Ubuntu machine, I reproduced the crash when 
>>> running under gdb (reproducing it is never an issue, finding the minimal 
>>> case is the issue). See below for gdb output. But my vm has no debug 
>>> information compiled, so it is not really useful. Can I download a vm with 
>>> debug info compiled from somewhere? I would prefer to avoid having to 
>>> download the sources and compile et cetera … 
>>> 
>>> Once I have such a VM I will make some time to further investigate, and 
>>> report results.
>>> 
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0xb8c2bc31 in ?? ()
>>> (gdb) bt
>>> #0  0xb8c2bc31 in ?? ()
>>> #1  0x080fc9f2 in primitiveNativeCall ()
>>> #2  0xb4fba770 in ?? ()
>>> #3  0xb503b05e in ?? ()
>>> #4  0xb503afcb in ?? ()
>>> #5  0xb5011abd in ?? ()
>>> #6  0xb4fba5c0 in ?? ()
>>> (gdb) 
>>> 
> 
> 
> 
> ---> Save our in-boxes! http://emailcharter.org  
> <---
> 
> Johan Fabry   -   http://pleiad.cl/~jfabry 
> PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
> Chile
> 

Re: [Pharo-users] Seaside on Pharo 5?

[Stephan Eggermont]

On 30/10/15 16:48, Yuriy Tymchuk wrote:

Is there a version of Seaside that works on Pharo5?


If you disable the deprecation warning for #subStrings:
you should be fine.

Stephan

Re: [Pharo-users] [ANN] Working with Pharo on the Raspberry Pi

[EuanM]

Thanks.  My medium-term plan is to run my Smalltalk app from a Pi - this was
encouraging!



--
View this message in context: 
http://forum.world.st/ANN-Working-with-Pharo-on-the-Raspberry-Pi-tp4857895p4858808.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] VM crash on Ubuntu 14.04

[Johan Fabry]

Ah those wonderful memory leaks … :-/ I will try to narrow down the possible 
source, but that is not going to be easy … It’s really a very specific setup 
that always crashes on me, so It must be a freaky combination of factors that 
triggers the issue. Running a Roassal visualization certainly is needed to 
crash, but apparently it’s not the only thing. I will keep trying to remove 
elements from the setup to see what the required combination is. 

> On Oct 31, 2015, at 07:38, Esteban Lorenzano  wrote:
> 
> not so bad… that actually means that you are running out of heap, badly :P
> and since I see a primitiveNativeCall there, most probably your (athens?) 
> program is leaking somewhere. 
> 
> Esteban
> 
>> On 30 Oct 2015, at 18:01, Johan Fabry > > wrote:
>> 
>> 
>> More bad luck I’m afraid. What can I do next?
>> 
>> Program received signal SIGSEGV, Segmentation fault.
>> 0xb8c0b92d in ?? ()
>> (gdb) p (void)printCallStack()
>> Cannot access memory at address 0x
>> (gdb) 
>> 
>>> On Oct 30, 2015, at 08:11, Esteban Lorenzano >> > wrote:
>>> 
>>> you can type 
>>> 
>>> p (void)printCallStack()
>>> 
>>> then you will have the active stack when crash happened. Is often a lot 
>>> more useful than the trace of the vm.
>>> 
>>> Esteban
>>> 
 On 29 Oct 2015, at 19:03, Johan Fabry > wrote:
 
 
 OK, back with access to the Ubuntu machine, I reproduced the crash when 
 running under gdb (reproducing it is never an issue, finding the minimal 
 case is the issue). See below for gdb output. But my vm has no debug 
 information compiled, so it is not really useful. Can I download a vm with 
 debug info compiled from somewhere? I would prefer to avoid having to 
 download the sources and compile et cetera … 
 
 Once I have such a VM I will make some time to further investigate, and 
 report results.
 
 Program received signal SIGSEGV, Segmentation fault.
 0xb8c2bc31 in ?? ()
 (gdb) bt
 #0  0xb8c2bc31 in ?? ()
 #1  0x080fc9f2 in primitiveNativeCall ()
 #2  0xb4fba770 in ?? ()
 #3  0xb503b05e in ?? ()
 #4  0xb503afcb in ?? ()
 #5  0xb5011abd in ?? ()
 #6  0xb4fba5c0 in ?? ()
 (gdb) 
 
>> 
>> 
>> 
>> ---> Save our in-boxes! http://emailcharter.org  
>> <---
>> 
>> Johan Fabry   -   http://pleiad.cl/~jfabry 
>> PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
>> Chile
>> 
> 



---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
Chile

Re: [Pharo-users] OSProcess seems to fail on my macos

[Dimitris Chloupis]

yes , git runs fine from command line. And yes I accepted the license. I
use filetree and git from command line to work with that repo now without
any issues.

On Sat, Oct 31, 2015 at 7:14 PM Johan Fabry  wrote:

> Hi,
>
> Did you try running the Xcode command line tools in a terminal? Sometimes
> when you do an upgrade you need to accept the license that pops up when you
> run these tools, and that causes this kind of issues. It happened to me a
> long time ago.
>
> On Oct 30, 2015, at 18:14, Dimitris Chloupis 
> wrote:
>
> I have several issues using gitfiletree, which in turn has issues with
> metacello trying to fetch git info about my git branch locally which I
> tracked back to OSProcess not executing on my macos.
>
> This started to happen as soon as I updated to latest XCODE and installed
> its latest command tools, anyone else with same issue ? I tried several
> OSProcess commands but they all return empty strings even though they
> complete with no errors.
>
> An expert help would be of great assistance, thanks ! I have reverted back
> to using filetree and doing my git commits manually via command line.
>
>
>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry   -   http://pleiad.cl/~jfabry
> PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University
> of Chile
>
>

Re: [Pharo-users] OSProcess seems to fail on my macos

[Johan Fabry]

Hi,

Did you try running the Xcode command line tools in a terminal? Sometimes when 
you do an upgrade you need to accept the license that pops up when you run 
these tools, and that causes this kind of issues. It happened to me a long time 
ago.

> On Oct 30, 2015, at 18:14, Dimitris Chloupis  wrote:
> 
> I have several issues using gitfiletree, which in turn has issues with 
> metacello trying to fetch git info about my git branch locally which I 
> tracked back to OSProcess not executing on my macos. 
> 
> This started to happen as soon as I updated to latest XCODE and installed its 
> latest command tools, anyone else with same issue ? I tried several OSProcess 
> commands but they all return empty strings even though they complete with no 
> errors. 
> 
> An expert help would be of great assistance, thanks ! I have reverted back to 
> using filetree and doing my git commits manually via command line. 



---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
Chile

Re: [Pharo-users] [ANN] Working with Pharo on the Raspberry Pi

[stepharo]

Jean-Baptiste did it and demoed it at ESUG at Cambridge.
He is now travelling and crashed his machine so may contact him at:
jbaptiste.arn...@gmail.com
He will be probably busy until wednesday fixing his machine and 
application to a new job.

Stef

Le 30/10/15 08:27, Tim Hendriks a écrit :

What I would like is access to the GPIO pins from Pharo…. It is possible from 
Scratch so someone (i am to stupid to do this) could maybe hack that into Pharo?

Tim



On 30 Oct 2015, at 16:22, Tim Hendriks  wrote:

Pharo5 works with fine with the squeak vm in Jessie. No error’s and much 
faster. Didn’t test it thoroughly.

Tim



On 26 Oct 2015, at 16:41, Attila Magyar  wrote:

Hi Torsten,

Have you tried the cogvm on the Pi? It is much faster than the stack vm. If
I remember correctly, I used this one last time:
http://www.mirandabanda.org/files/Cog/VM/VM.r3427/cogspurlinuxhtARM-15.33.3427.tgz

Attila



--
View this message in context: 
http://forum.world.st/ANN-Working-with-Pharo-on-the-Raspberry-Pi-tp4857895p4858039.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

[Pharo-users] [ANN] RenoirSt 2.0.0 released!

[Gabriel Cotelli]

Hi,
I'm announcing a new official release of RenoirSt.
See the announcement and changelog


Regarsd,
Gabriel

Re: [Pharo-users] VM crash on Ubuntu 14.04

[Ronie Salgado]

Hi Johan,

Perhaps I can try to help you debugging with gdb. Are you using a 32 bits
or 64 bits Ubuntu ?
We should start by building a debug Pharo VM. Do you have some time during
Monday or Wednesday in your office?.

Greetings,
Ronie

2015-10-31 22:00 GMT-03:00 stepharo :

> Why do you say that johan?
> Everybody is busy and has its own agenda. I'm sure that esteban would love
> to have the time
> to just wait for helping people. This is not the case and the dragons he
> is fighting against are
> quite large and venomous.
> So the suggestion of Ben is good because else I do not see how people can
> help you.
>
> Stef
>
> Le 24/10/15 12:32, Johan Fabry a écrit :
>
> Ben, thanks for replying but since no VM guys are following up on this,
>> apparently, it does not make much sense for me to go this way.
>>
>> Guys, am I to assume there is not help for me on this topic?
>>
>> On Oct 23, 2015, at 11:03, Ben Coman  wrote:
>>>
>>> On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry 
>>> wrote:
>>>
 Hi all,

 I am having some unpleasant experiences on Ubuntu 14.04 (experimenting
 with Live Robot Programming on PhaROS). The VM crashes after a random
 amount of time (< 25 minutes), with no clear sequence of steps on how to
 reproduce the crash. I am using Pharo 4 (Pharo 40622 as installed by
 PhaROS) + Roassal which required an install of libcairo2:i386 . VM version
 details below.

 There is no printout on stdout, and the debug.log does not contain
 recent entries (timestamp is always some minutes before the actual crash
 happens).

 Is this a known problem? If so, how can I fix it, and if not how can I
 provide more debugging info?

 Thanks in advance!

>>> I'm not much help since I haven't done these myself, but just some
>>> ideas (maybe someone can add more details)
>>> * compile and run a debug vm
>>> * trace all function calls, http://tinyurl.com/gdb-trace-all
>>>
>>>
>>
>> ---> Save our in-boxes! http://emailcharter.org <---
>>
>> Johan Fabry   -   http://pleiad.cl/~jfabry
>> PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University
>> of Chile
>>
>>
>>
>>
>
>

Re: [Pharo-users] VM crash on Ubuntu 14.04

[Ben Coman]

On Fri, Oct 30, 2015 at 2:03 AM, Johan Fabry  wrote:
>
> OK, back with access to the Ubuntu machine, I reproduced the crash when
> running under gdb (reproducing it is never an issue, finding the minimal
> case is the issue). See below for gdb output. But my vm has no debug
> information compiled, so it is not really useful. Can I download a vm with
> debug info compiled from somewhere? I would prefer to avoid having to
> download the sources and compile et cetera …

Why not give it a go? :)  I found it dead simple to compile the VM for
the first time following instructions at...
[1] https://github.com/pharo-project/pharo-vm

This was on OSX and the only problem I had was _not_ following the
instructions and using XCode 10.9 instead of 10.6.
I can't speak for Ubuntu but its the reference Unix platform.  I guess
you'll get better support getting started with the standard
instructions (since we'd like them "perfect" and more people will be
able to replicate a problem with these than replicate your unique
problem)

One thing though, could someone update [1] to describe how to get a
debug VM, since that must be a common reason someone wants to compile
their own VM for the first time.  I hunted around for some info but
could only find tips from a few years ago and I'm not sure if they
still apply

Debug a VM (by Mariano)
https://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-using-git-and-cmakevmmaker/
https://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/
https://vimeo.com/22485382 (PharoCast)

Debugging assembly in Pharo VM with GDB (by Melkyades)
http://melkyades.blogspot.com.au/2013/07/debugging-assembly-in-pharo-vm-with-gdb.html

cheers -ben

>
> Once I have such a VM I will make some time to further investigate, and
> report results.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb8c2bc31 in ?? ()
> (gdb) bt
> #0  0xb8c2bc31 in ?? ()
> #1  0x080fc9f2 in primitiveNativeCall ()
> #2  0xb4fba770 in ?? ()
> #3  0xb503b05e in ?? ()
> #4  0xb503afcb in ?? ()
> #5  0xb5011abd in ?? ()
> #6  0xb4fba5c0 in ?? ()
> (gdb)
>
> On Oct 27, 2015, at 19:09, Nicolai Hess  wrote:
>
>
>
> 2015-10-26 15:03 GMT+01:00 Johan Fabry :
>>
>> Hi Nicolai,
>>
>> thanks for following up on this.
>>
>> I am in the process of determining what causes the crash. I fear that to
>> reproduce the problem you will need to have ROS installed, I have not yet
>> been able to reproduce it without ROS running. I do not want to inflict the
>> installation of ROS on you without being 100% sure.
>>
>> I am using Roassal because this is for Live Robot Programming
>> (http://pleiad.cl/LRP) which uses a dynamic visualization of the running
>> code. To reproduce the bug (until now) I need to develop code in LRP when
>> using ROS, and then it happens randomly. I realize that this is too much to
>> ask for an outsider to reproduce the bug (I did not expect anybody to
>> download and install PhaROS to try to reproduce, thanks for that!!).
>>
>> Can you inform me how I can get you more useful debug info to you? I will
>> keep trying to find minimal steps to reproduce in the mean time.
>
>
> No, the best we can hope for is a crash when it is running from debugger,
> you can start the vm with a debugger or attach the debugger to a running
> process. If we  are lucky, the debugger will show a stacktrace.
>
>>
>>
>> On Oct 24, 2015, at 19:45, Nicolai Hess  wrote:
>>
>> Can you provide the image file.
>> What exactly runs in the image (does it depend on ROS or
>> does it crash even without it). For what do you
>> use Roassal in this environment.
>> Can you reproduce the crash with a clean image (and maybe loading
>> some package - without all of the ROS-stuff?
>> (I just followed the installation guide for PhaROS, but I have no idea
>> how to go from here to do anything to reproduce the crash).
>>
>>
>>
>> 2015-10-24 21:32 GMT+02:00 Johan Fabry :
>>>
>>>
>>> Ben, thanks for replying but since no VM guys are following up on this,
>>> apparently, it does not make much sense for me to go this way.
>>>
>>> Guys, am I to assume there is not help for me on this topic?
>>>
>>> > On Oct 23, 2015, at 11:03, Ben Coman  wrote:
>>> >
>>> > On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry 
>>> > wrote:
>>> >> Hi all,
>>> >>
>>> >> I am having some unpleasant experiences on Ubuntu 14.04 (experimenting
>>> >> with Live Robot Programming on PhaROS). The VM crashes after a random 
>>> >> amount
>>> >> of time (< 25 minutes), with no clear sequence of steps on how to 
>>> >> reproduce
>>> >> the crash. I am using Pharo 4 (Pharo 40622 as installed by PhaROS) + 
>>> >> Roassal
>>> >> which required an install of libcairo2:i386 . VM version details below.
>>> >>
>>> >> There is no printout on stdout, and the debug.log does not contain
>>> >> recent entries (timestamp is always some