[Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream

[Cyril Ferlicot D.]

Hello!

I have a Jenkins build for MaterialDesignLite and the Pharo 7 build
never end.

I load the code via the command line "eval" with the "--save" parameter
and a Metacello command.

While adding some log I found the problem.

It comes from this method:

EvaluateCommandLineHandler>>evaluate: aStream
| result |
[
result := Smalltalk compiler evaluate: aStream.
self hasSessionChanged
ifFalse: [
self stdout
print: result;
lf ] ]
on: Error
do: [ :error | self handleError: error ]

In Pharo 6 it ends perfectly.

In Pharo 7 there is an error and we end up in the catch.

Here is the stack I could isolate:


MessageNotUnderstood(Exception)>>signal
UndefinedObject(Object)>>doesNotUnderstand: #'>='
AnObsoleteZnCrPortableWriteStream(WriteStream)>>nextPut:
[ :v | self nextPut: v ] in
AnObsoleteZnCrPortableWriteStream(Stream)>>nextPutAll:
ByteSymbol(SequenceableCollection)>>do:
AnObsoleteZnCrPortableWriteStream(Stream)>>nextPutAll:
AnObsoleteZnCrPortableWriteStream(WriteStream)>>nextPutAll:
MultiByteFileStream(StandardFileStream)>>printOn:
AnObsoleteZnCrPortableWriteStream(Stream)>>print:
VTermOutputDriver>>print:

I have no idea how to correct this and it's pretty late now. Maybe
someone will know :)

https://pharo.fogbugz.com/f/cases/21566/EvaluateCommandLineHandler-is-broken-in-Pharo-7

-- 
Cyril Ferlicot
https://ferlicot.fr



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-dev] Loading configuration of spur

[Stephane Ducasse]

I was reading the medium article of andrei and just discussing with
clement on how can we improve the tooling for the VM bug chasing and
other activities and this would be a really great improvement. I
should watch the videos of clement on debugging the JIT first.

On Mon, Mar 12, 2018 at 8:03 PM, Sven Van Caekenberghe  wrote:
>
>
>> On 12 Mar 2018, at 19:50, Eliot Miranda  wrote:
>>
>> Hi Sven,
>>
>>> On Mar 12, 2018, at 10:46 AM, Sven Van Caekenberghe  wrote:
>>>
>>>
>>>
 On 12 Mar 2018, at 17:22, Eliot Miranda  wrote:

 Hi Javier,


> On Mar 11, 2018, at 11:14 AM, Javier Pimás  
> wrote:
>
> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 
> image, is that supported?

 Both Clément and I use Squeak for vm development at the moment.  We don't 
 have the cycles to keep it working in both as yet.
>>>
>>> Which is a pity for a VM that is called Open Smalltalk.
>>>
>>> The net result is that you are missing out on a much larger base of curious 
>>> developers and potential contributors.
>>
>> Agreed.  But it is hopefully only temporary.  The package did load in Pharo 
>> a few years ago, and the prospect of using GT tools is an incentive for 
>> getting this working again.  As the multiple bytecode set support stabilizes 
>> in both Squeak and Pharo I expect it to get easier to maintain VMMaker.oscog 
>> in both dialects.  VMMaker.oscog had to contain many patches to support the 
>> CM development of the SistaV1 bytecode set, and the load failure Javier is 
>> seeing is related to this.  As time allows I am eliminating these patches.  
>> So hopefully it'll load in Pharo soon.
>
> That would be really great.
>
> I have this snippet that doesn't work:
>
> Metacello new
>   filetreeDirectory: '../VMMaker/mc';
>   baseline: 'Spur';
>   load
>
> where ../VMMaker/mc is a clone of the official pharo repo at github.
>
> Cheers,
> pocho
>
> --
> Javier Pimás
> Ciudad de Buenos Aires
>
>

Re: [Pharo-dev] Loading configuration of spur

[Sven Van Caekenberghe]

> On 12 Mar 2018, at 19:50, Eliot Miranda  wrote:
> 
> Hi Sven,
> 
>> On Mar 12, 2018, at 10:46 AM, Sven Van Caekenberghe  wrote:
>> 
>> 
>> 
>>> On 12 Mar 2018, at 17:22, Eliot Miranda  wrote:
>>> 
>>> Hi Javier,
>>> 
>>> 
 On Mar 11, 2018, at 11:14 AM, Javier Pimás  
 wrote:
 
 Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 
 image, is that supported?
>>> 
>>> Both Clément and I use Squeak for vm development at the moment.  We don't 
>>> have the cycles to keep it working in both as yet.
>> 
>> Which is a pity for a VM that is called Open Smalltalk. 
>> 
>> The net result is that you are missing out on a much larger base of curious 
>> developers and potential contributors.
> 
> Agreed.  But it is hopefully only temporary.  The package did load in Pharo a 
> few years ago, and the prospect of using GT tools is an incentive for getting 
> this working again.  As the multiple bytecode set support stabilizes in both 
> Squeak and Pharo I expect it to get easier to maintain VMMaker.oscog in both 
> dialects.  VMMaker.oscog had to contain many patches to support the CM 
> development of the SistaV1 bytecode set, and the load failure Javier is 
> seeing is related to this.  As time allows I am eliminating these patches.  
> So hopefully it'll load in Pharo soon.

That would be really great.

 I have this snippet that doesn't work:
 
 Metacello new
   filetreeDirectory: '../VMMaker/mc';
   baseline: 'Spur';
   load
 
 where ../VMMaker/mc is a clone of the official pharo repo at github.
 
 Cheers,
 pocho
 
 -- 
 Javier Pimás
 Ciudad de Buenos Aires

Re: [Pharo-dev] Loading configuration of spur

[Eliot Miranda]

Hi Sven,

> On Mar 12, 2018, at 10:46 AM, Sven Van Caekenberghe  wrote:
> 
> 
> 
>> On 12 Mar 2018, at 17:22, Eliot Miranda  wrote:
>> 
>> Hi Javier,
>> 
>> 
>>> On Mar 11, 2018, at 11:14 AM, Javier Pimás  
>>> wrote:
>>> 
>>> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 
>>> image, is that supported?
>> 
>> Both Clément and I use Squeak for vm development at the moment.  We don't 
>> have the cycles to keep it working in both as yet.
> 
> Which is a pity for a VM that is called Open Smalltalk. 
> 
> The net result is that you are missing out on a much larger base of curious 
> developers and potential contributors.

Agreed.  But it is hopefully only temporary.  The package did load in Pharo a 
few years ago, and the prospect of using GT tools is an incentive for getting 
this working again.  As the multiple bytecode set support stabilizes in both 
Squeak and Pharo I expect it to get easier to maintain VMMaker.oscog in both 
dialects.  VMMaker.oscog had to contain many patches to support the CM 
development of the SistaV1 bytecode set, and the load failure Javier is seeing 
is related to this.  As time allows I am eliminating these patches.  So 
hopefully it'll load in Pharo soon.

> 
>>> I have this snippet that doesn't work:
>>> 
>>> Metacello new
>>>filetreeDirectory: '../VMMaker/mc';
>>>baseline: 'Spur';
>>>load
>>> 
>>> where ../VMMaker/mc is a clone of the official pharo repo at github.
>>> 
>>> Cheers,
>>> pocho
>>> 
>>> -- 
>>> Javier Pimás
>>> Ciudad de Buenos Aires
>> 
> 
> 

Re: [Pharo-dev] Loading configuration of spur

[Sven Van Caekenberghe]

> On 12 Mar 2018, at 17:22, Eliot Miranda  wrote:
> 
> Hi Javier,
> 
> 
>> On Mar 11, 2018, at 11:14 AM, Javier Pimás  
>> wrote:
>> 
>> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 
>> image, is that supported?
> 
> Both Clément and I use Squeak for vm development at the moment.  We don't 
> have the cycles to keep it working in both as yet.

Which is a pity for a VM that is called Open Smalltalk. 

The net result is that you are missing out on a much larger base of curious 
developers and potential contributors.

>> I have this snippet that doesn't work:
>> 
>> Metacello new
>>  filetreeDirectory: '../VMMaker/mc';
>>  baseline: 'Spur';
>>  load
>> 
>> where ../VMMaker/mc is a clone of the official pharo repo at github.
>> 
>> Cheers,
>> pocho
>> 
>> -- 
>> Javier Pimás
>> Ciudad de Buenos Aires
> 

Re: [Pharo-dev] Loading configuration of spur

[Eliot Miranda]

> On Mar 11, 2018, at 11:14 AM, Javier Pimás  wrote:
> 
> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 
> image, is that supported? I have this snippet that doesn't work:
> 
> Metacello new
>   filetreeDirectory: '../VMMaker/mc';
>   baseline: 'Spur';
>   load
> 
> where ../VMMaker/mc is a clone of the official pharo repo at github.

and vm development is in VMMaker.oscog in Monticello at 
source.squeak.org/VMMaker

> 
> Cheers,
> pocho
> 
> -- 
> Javier Pimás
> Ciudad de Buenos Aires

Re: [Pharo-dev] Loading configuration of spur

[Eliot Miranda]

Hi Javier,


> On Mar 11, 2018, at 11:14 AM, Javier Pimás  wrote:
> 
> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 
> image, is that supported?

Both Clément and I use Squeak for vm development at the moment.  We don't have 
the cycles to keep it working in both as yet.

> I have this snippet that doesn't work:
> 
> Metacello new
>   filetreeDirectory: '../VMMaker/mc';
>   baseline: 'Spur';
>   load
> 
> where ../VMMaker/mc is a clone of the official pharo repo at github.
> 
> Cheers,
> pocho
> 
> -- 
> Javier Pimás
> Ciudad de Buenos Aires

Re: [Pharo-dev] [Pharo-users] feenk log

[Alistair Grant]

On 11 March 2018 at 21:01, Tudor Girba  wrote:
> Hi,
>
> Here is an update of the work on Bloc, Brick and GT. As always, please do let 
> us know what you think.
>
> [snip/]
>
> - Andrei put together a beautiful description of a scenario in which an 
> application is molded interactively in the Playground & Inspector. The 
> subject is face recognition, and the resulting code is both functional and 
> explainable. This is intended as a tutorial material that shows what moldable 
> development means and how it changes the way we program:
> https://twitter.com/feenkcom/status/972907051448979458

The GToolkit has certainly influenced how I program - and this is a
great article that lays it out quite clearly.  If I'm developing a new
application the first few iterations of the UI are pretty much always
extensions to the inspector.

I also enjoyed Tudor's interview on No Fluff Just Stuff which
discusses a real world use of this:

- Podcast audio:
https://player.fm/series/no-fluff-just-stuff/changing-the-way-we-code-w-tudor-girba
- No Fluff Just Stuff: https://nofluffjuststuff.com/home/main

Thanks!
Alistair

[Pharo-dev] FORGET WHAT I SAID: THERE ARE NOT NEW STABLES

[Esteban Lorenzano]

because new stables were not stable :)

Esteban

Re: [Pharo-dev] [ANN] New stable VMs promoted for both 7.0a and 6.1

[Esteban Lorenzano]

meh :/
I restored the old stable VMs

honestly, this thing of not having a stable and development branch on VM sucks. 

Esteban

> On 12 Mar 2018, at 14:05, Alistair Grant  wrote:
> 
> On 12 March 2018 at 13:33, Esteban Lorenzano  wrote:
>> Hi,
>> 
>> as the subject said, I promoted new VMs from last week latests on both 
>> version 6.1 and 7.0a.
>> this should fix some ongoing problems with versioning.
>> 
>> please let me know if something is not working as expected.
>> 
>> cheers!
>> Esteban
>> 
>> ps: I don’t know what I’m thinking about… of course you will let me know if 
>> something is not working as expected! ;)
> 
> Maybe the jenkins build process... :-)
> 
> .finished baselineInconsistency detected by ld.so: dl-close.c: 811:
> _dl_close: Assertion `map->l_init_called' failed!
> 
> Tobias hopes he's fixed it in 802de0a1b, but I haven't tested it yet.
> The travis build for it should finish in about 15 minutes.
> 
> Cheers,
> Alistair
> 

Re: [Pharo-dev] Loading configuration of spur

[Javier Pimás]

On Mon, Mar 12, 2018 at 9:25 AM, Guillermo Polito  wrote:

> Hmm no idea. The best I can think about is that that VMMaker version is
> old (Pharo5 is at least 2 years old) and there is probably a dependency
> between VMMaker and the compiler (thus that BytecodeEncoder ref). IF
> VMMaker is overriding some methods in BytecodeEncoder, then what is
> happenning is that you're breaking the compiler (?).
>

sounds very much like what i'm seeing.


>
> In any case, again, that is not the official VMMaker repository but a
> mirror.
>

should I use the one here? http://source.squeak.org/VMMaker

Do you still use the one in github? Because if not I would recommend
removing it as it is a bit misleading.


> On Mon, Mar 12, 2018 at 11:53 AM, Javier Pimás  > wrote:
>
>> Oh I forgot to write down the actual error. There is a MNU for
>> BytecodeEncoder class>>#isExtension: which seems to have been removed from
>> the image. It is a bit different to typical doesNotUnderstand errors
>> because it opens an emergency evaluator and leaves the image unusable.
>>
>> On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito <
>> guillermopol...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'll Esteban answer better but I don't know if that VMMaker mirror is
>>> up to date.
>>>
>>> Taking a look at the images/newImage.sh script, it is using Pharo5.0.
>>> But I see no reason for it not working on latest versions. Probably some
>>> patches are required...
>>>
>>> What is your error?
>>>
>>>
>>> On Sun, Mar 11, 2018 at 7:14 PM, Javier Pimás <
>>> elpochodelage...@gmail.com> wrote:
>>>
 Ok, now I moved forward but cannot load vmmaker sources into a pharo 61
 image, is that supported? I have this snippet that doesn't work:

 Metacello new
 filetreeDirectory: '../VMMaker/mc';
 baseline: 'Spur';
 load

 where ../VMMaker/mc is a clone of the official pharo repo at github.

 Cheers,
 pocho

 --
 Javier Pimás
 Ciudad de Buenos Aires

>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> Guille Polito
>>>
>>> Research Engineer
>>>
>>> Centre de Recherche en Informatique, Signal et Automatique de Lille
>>>
>>> CRIStAL - UMR 9189
>>>
>>> French National Center for Scientific Research - *http://www.cnrs.fr
>>> *
>>>
>>>
>>> *Web:* *http://guillep.github.io* 
>>>
>>> *Phone: *+33 06 52 70 66 13 <06%2052%2070%2066%2013>
>>>
>>
>>
>>
>> --
>> Javier Pimás
>> Ciudad de Buenos Aires
>>
>
>
>
> --
>
>
>
> Guille Polito
>
> Research Engineer
>
> Centre de Recherche en Informatique, Signal et Automatique de Lille
>
> CRIStAL - UMR 9189
>
> French National Center for Scientific Research - *http://www.cnrs.fr
> *
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <06%2052%2070%2066%2013>
>



-- 
Javier Pimás
Ciudad de Buenos Aires

Re: [Pharo-dev] [ANN] New stable VMs promoted for both 7.0a and 6.1

[Alistair Grant]

On 12 March 2018 at 13:33, Esteban Lorenzano  wrote:
> Hi,
>
> as the subject said, I promoted new VMs from last week latests on both 
> version 6.1 and 7.0a.
> this should fix some ongoing problems with versioning.
>
> please let me know if something is not working as expected.
>
> cheers!
> Esteban
>
> ps: I don’t know what I’m thinking about… of course you will let me know if 
> something is not working as expected! ;)

Maybe the jenkins build process... :-)

.finished baselineInconsistency detected by ld.so: dl-close.c: 811:
_dl_close: Assertion `map->l_init_called' failed!

Tobias hopes he's fixed it in 802de0a1b, but I haven't tested it yet.
The travis build for it should finish in about 15 minutes.

Cheers,
Alistair

[Pharo-dev] [ANN] New stable VMs promoted for both 7.0a and 6.1

[Esteban Lorenzano]

Hi,

as the subject said, I promoted new VMs from last week latests on both version 
6.1 and 7.0a.
this should fix some ongoing problems with versioning. 

please let me know if something is not working as expected.

cheers!
Esteban

ps: I don’t know what I’m thinking about… of course you will let me know if 
something is not working as expected! ;)

Re: [Pharo-dev] Loading configuration of spur

[Guillermo Polito]

Hmm no idea. The best I can think about is that that VMMaker version is old
(Pharo5 is at least 2 years old) and there is probably a dependency between
VMMaker and the compiler (thus that BytecodeEncoder ref). IF VMMaker is
overriding some methods in BytecodeEncoder, then what is happenning is that
you're breaking the compiler (?).

In any case, again, that is not the official VMMaker repository but a
mirror.

On Mon, Mar 12, 2018 at 11:53 AM, Javier Pimás 
wrote:

> Oh I forgot to write down the actual error. There is a MNU for
> BytecodeEncoder class>>#isExtension: which seems to have been removed from
> the image. It is a bit different to typical doesNotUnderstand errors
> because it opens an emergency evaluator and leaves the image unusable.
>
> On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito <
> guillermopol...@gmail.com> wrote:
>
>> Hi,
>>
>> I'll Esteban answer better but I don't know if that VMMaker mirror is up
>> to date.
>>
>> Taking a look at the images/newImage.sh script, it is using Pharo5.0. But
>> I see no reason for it not working on latest versions. Probably some
>> patches are required...
>>
>> What is your error?
>>
>>
>> On Sun, Mar 11, 2018 at 7:14 PM, Javier Pimás > > wrote:
>>
>>> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61
>>> image, is that supported? I have this snippet that doesn't work:
>>>
>>> Metacello new
>>> filetreeDirectory: '../VMMaker/mc';
>>> baseline: 'Spur';
>>> load
>>>
>>> where ../VMMaker/mc is a clone of the official pharo repo at github.
>>>
>>> Cheers,
>>> pocho
>>>
>>> --
>>> Javier Pimás
>>> Ciudad de Buenos Aires
>>>
>>
>>
>>
>> --
>>
>>
>>
>> Guille Polito
>>
>> Research Engineer
>>
>> Centre de Recherche en Informatique, Signal et Automatique de Lille
>>
>> CRIStAL - UMR 9189
>>
>> French National Center for Scientific Research - *http://www.cnrs.fr
>> *
>>
>>
>> *Web:* *http://guillep.github.io* 
>>
>> *Phone: *+33 06 52 70 66 13 <06%2052%2070%2066%2013>
>>
>
>
>
> --
> Javier Pimás
> Ciudad de Buenos Aires
>



-- 



Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

Re: [Pharo-dev] Pharo 7.0 does not includes "Metacello support for GitFileTree metadata-less mode"

[Juraj Kubelka]

Hi!

thank you, it works!

Juraj

> El 27-02-2018, a las 20:19, Cyril Ferlicot D.  
> escribió:
> 
> Le 25/02/2018 à 23:07, Cyril Ferlicot D. a écrit :
>> Hi!
>> 
>> This support is in this PR:
>> 
>> https://github.com/pharo-project/pharo/pull/950
>> 
>> It was not added in Pharo 7 during the last sync but was in Pharo 6.1.
>> 
>> I hope in the future we will depend on Metacello as a project during the
>> bootstrap instead of having the sources directly in the Pharo
>> repository. It will help but it needs work.
>> 
> 
> 
> Hi!
> 
> It is integrated. Can you check in the latest Pharo please?
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr
> 

Re: [Pharo-dev] Loading configuration of spur

[Javier Pimás]

Oh I forgot to write down the actual error. There is a MNU for
BytecodeEncoder class>>#isExtension: which seems to have been removed from
the image. It is a bit different to typical doesNotUnderstand errors
because it opens an emergency evaluator and leaves the image unusable.

On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito  wrote:

> Hi,
>
> I'll Esteban answer better but I don't know if that VMMaker mirror is up
> to date.
>
> Taking a look at the images/newImage.sh script, it is using Pharo5.0. But
> I see no reason for it not working on latest versions. Probably some
> patches are required...
>
> What is your error?
>
>
> On Sun, Mar 11, 2018 at 7:14 PM, Javier Pimás 
> wrote:
>
>> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61
>> image, is that supported? I have this snippet that doesn't work:
>>
>> Metacello new
>> filetreeDirectory: '../VMMaker/mc';
>> baseline: 'Spur';
>> load
>>
>> where ../VMMaker/mc is a clone of the official pharo repo at github.
>>
>> Cheers,
>> pocho
>>
>> --
>> Javier Pimás
>> Ciudad de Buenos Aires
>>
>
>
>
> --
>
>
>
> Guille Polito
>
> Research Engineer
>
> Centre de Recherche en Informatique, Signal et Automatique de Lille
>
> CRIStAL - UMR 9189
>
> French National Center for Scientific Research - *http://www.cnrs.fr
> *
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <06%2052%2070%2066%2013>
>



-- 
Javier Pimás
Ciudad de Buenos Aires

Re: [Pharo-dev] pharo64+git crash

[Esteban Lorenzano]

I think I will declare new stables today. 
this is becoming a too confusing, and latest VMs are working fine, AFAIK ;)

Esteban

> On 11 Mar 2018, at 19:41, Thierry Goubier  wrote:
> 
> Le 11/03/2018 à 18:09, Javier Pimás a écrit :
>> Didn't work. Tried also with vmT70 and vmI70 and neither did work. Sometimes 
>> they segfault, sometimes they hang using 100% cpu. I noticed that being for 
>> pharo7 those vms seemed pretty old (aug-2017), so I tried vmTLatest70 and 
>> that one finally worked.
> 
> Oh :( Thank you for pointing that it worked with the latest 70 vm.
> 
> I must admit that I'm using directly downloaded recent vms to avoid that same 
> segfault and not the pharo.org  VMs, but the process for 
> setting them is a bit complex. So I hoped that the problem was solved with 
> the Pharo 7 VMs, which are newer.
> 
> Thierry
> 
>> On Sun, Mar 11, 2018 at 6:31 AM, Thierry Goubier >  > >> wrote:
>>Hi Javier,
>>can you try with a 64 bits Pharo 7 vm
>>(http://get.pharo.org/64/vm70 )? The Pharo 
>> 6 64bits vm used to have
>>segfaults upon code loading.
>>Regards,
>>Thierry
>>Le 10/03/2018 à 22:59, Javier Pimás a écrit :
>>Hi, I wonder if I'm doing something wrong or using a wrong version:
>>I download a pharo image (spur64) from
>>http://files.pharo.org/get-files/61/pharo64.zip 
>> 
>>> >
>>and a 64 bit vm from:
>>get.pharo.org/64/vm61  
>> >
>>
>>Then I try to load a git repo like this:
>>./pharo Pharo.image ../scripts/loadSqueakNOSVM.st
>>where the script just says
>>"Based on the same file from the pharo-vm project"
>>Author useAuthor: 'LoadVMMaker' during: [
>>Metacello new
>>  baseline: #Nopsys;
>>  repository: 'github://nopsys/CogNOS/VM-src';
>>  load ].
>>(Smalltalk saveAs: 'generator')
>>  ifFalse: [ Smalltalk snapshot: false andQuit: true ].
>>and it crashes with the log pasted below. I cannot even load the
>>code, any clue?
>>Cheers,
>>Pocho
>>
>>Fetched -> BaselineOfNopsys-GitHub.1520523060 ---
>>g...@github.com:nopsys/CogNOS.git[master] ---
>>/CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit)
>>Loaded -> BaselineOfNopsys-GitHub.1520523060 ---
>>g...@github.com:nopsys/CogNOS.git[master] ---
>>/CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit)
>>Loading baseline of BaselineOfNopsys...
>>Fetched -> SqueakNOS-VM-GitHub.1520523060 ---
>>g...@github.com:nopsys/CogNOS.git[master] ---
>>/CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit)
>>Fetched -> BaselineOfSpur-EstebanLorenzano.4 ---
>>filetree:///CogNOS/VMMaker/mc [:] --- filetree:///CogNOS/VMMaker/mc
>>Segmentation fault Sat Mar 10 18:36:05 2018
>>/CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo
>>Pharo VM version: 5.0-201707201942  Thu Jul 20 20:40:54 UTC 2017
>>gcc 4.6.3 [Production Spur 64-bit VM]
>>Built from: CoInterpreter VMMaker.oscog-eem.2254 uuid:
>>4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017
>>With: StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid:
>>2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
>>Revision: VM: 201707201942
>>https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>> 
>>> > $ Date:
>>Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942
>>https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>> 
>> $
>>Build host: Linux
>>testing-gce-74d10329-bbfd-42e5-8995-b0e3a68c73cb
>>3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06
>>UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>>plugin path: /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942
>>[default: /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/]
>>C stack backtrace & registers:
>>rax 0x0c1c5f40 rbx 0x0c1c5dd0 rcx 0x0c1c5ff8 rdx 0x0c1c5e88
>>rdi 0x0c1c5ba8 rsi 0x0c1c5ba8 rbp 0x0c1c5d18 rsp 0x0c1c60b0
>>r8  0x0c1c55e8 r9  0x0c1c56a0 r10 

Re: [Pharo-dev] Loading configuration of spur

[Guillermo Polito]

Hi,

I'll Esteban answer better but I don't know if that VMMaker mirror is up to
date.

Taking a look at the images/newImage.sh script, it is using Pharo5.0. But I
see no reason for it not working on latest versions. Probably some patches
are required...

What is your error?


On Sun, Mar 11, 2018 at 7:14 PM, Javier Pimás 
wrote:

> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61
> image, is that supported? I have this snippet that doesn't work:
>
> Metacello new
> filetreeDirectory: '../VMMaker/mc';
> baseline: 'Spur';
> load
>
> where ../VMMaker/mc is a clone of the official pharo repo at github.
>
> Cheers,
> pocho
>
> --
> Javier Pimás
> Ciudad de Buenos Aires
>



-- 



Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

[Pharo-dev] [Pharo 7.0-dev] Build #689: 21563 Two small cleanups in InstructionStream

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #689 was: SUCCESS.

The Pull Request #1088 was integrated: "21563 Two small cleanups in 
InstructionStream"
Pull request url: https://github.com/pharo-project/pharo/pull/1088

Issue Url: https://pharo.fogbugz.com/f/cases/21563
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/689/

[Pharo-dev] Esteban's ChangeLog week of 5 March 2018

[estebanlm]

Hello!

This is my weekly ChangeLog, from 5 March 2018 to 11 March 2018.
You can see it in a better format by going here: 
http://log.smallworks.eu/web/search?from=5/3/2018=11/3/2018

ChangeLog
=

5 March 2018:
-

*Today I worked on details of Pull/Push views, and I fixed some pending 
issues with all the others.

As a side note, I added badges to my toolbars ;)
Is not finished yet (I guess it will be tomorrow), but is a good way to 
present certain information.


cheers! 
Esteban

[Pharo-dev] [Pharo 7.0-dev] Build #688: 21564 TraitBuilderEnhancer should use utilities protocol

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #688 was: SUCCESS.

The Pull Request #1089 was integrated: "21564 TraitBuilderEnhancer should use 
utilities protocol"
Pull request url: https://github.com/pharo-project/pharo/pull/1089

Issue Url: https://pharo.fogbugz.com/f/cases/21564
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/688/