January 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Setting a project with smtalltalkCI

by Gabriel Cotelli

Thank you Esteban, that was the problem. I overlooked it like 5 times... On Fri, Jan 13, 2017 at 6:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > I think the comma here: > > #categories : [ ''RenoirSt*'' ], > > is the offending one :) > > Esteban > > On 13 Jan 2017, at 21:58, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > Hi! anyone with smalltalkCI experience? > > I'm trying to setup travis CI integration for one of my projects ( > https://github.com/ba-st/RenoirSt/tree/smalltalk_ci) and I'm getting a > cryptic error on the builds: https://travis-ci.org/ba-st/ > RenoirSt/jobs/191751457 > > Any hints are welcome. > > Thanks, Gabriel > > >

Jan. 13, 2017

Re: [Pharo-dev] Setting a project with smtalltalkCI

by Esteban Lorenzano

I think the comma here: #categories : [ ''RenoirSt*'' ], is the offending one :) Esteban > On 13 Jan 2017, at 21:58, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > Hi! anyone with smalltalkCI experience? > > I'm trying to setup travis CI integration for one of my projects (https://github.com/ba-st/RenoirSt/tree/smalltalk_ci <https://github.com/ba-st/RenoirSt/tree/smalltalk_ci>) and I'm getting a cryptic error on the builds: https://travis-ci.org/ba-st/RenoirSt/jobs/191751457 <https://travis-ci.org/ba-st/RenoirSt/jobs/191751457> > > Any hints are welcome. > > Thanks, Gabriel

Jan. 13, 2017

Setting a project with smtalltalkCI

by Gabriel Cotelli

Hi! anyone with smalltalkCI experience? I'm trying to setup travis CI integration for one of my projects ( https://github.com/ba-st/RenoirSt/tree/smalltalk_ci) and I'm getting a cryptic error on the builds: https://travis-ci.org/ba-st/RenoirSt/jobs/191751457 Any hints are welcome. Thanks, Gabriel

Jan. 13, 2017

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

by stepharong

On Wed, 11 Jan 2017 12:48:43 +0100, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > OK, thanks, you are right; I was confused by the new filter option in > senders, somehow I assumed the list was not longer (and I ignored the > scroll bar) - weird./mail/ yes it happens to me a lot and it is annoying.

Jan. 13, 2017

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

by stepharong

can you open a bug entry. I'm dreaming about a Object with far less funky methods. On Wed, 11 Jan 2017 09:55:06 +0100, Torsten Bergmann <astares(a)gmx.de> wrote: >> But why the hell would there be a Object>>#head ?! >> >> IMHO such general selectors at this level should not be used unless >> there is a very good reason to do so. >> > > Yes - some Morphic addition. Version says: BenjaminVanRyseghem in 2013 > Only used in MorphTreeNodeMorph and to me this smells. We should nuke it. > > Thx > T. > -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 13, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by stepharong

thanks a lot guille for your positive attitude. You give me the energy to continue when I'm sometimes tired. :) > Hi all, > > Just wanted to share this: > > https://github.com/guillep/pharo-snapcraft > > It is basically the code to generate a snap package of the pharo-vm > using snapcraft. Using this, the VM is generated and packaged with all > dependencies. This should help in running pharo in >different linux > distributions. > > I invite you to check it, report problems and submit fixes. > > Cheers, > Guille -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 13, 2017

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

by Aliaksei Syrel

UPD: Works using 497 windows vm: http://files.pharo.org/vm/pharo-spur32/win/497.zip. Something was changed recently... Cheers, Alex On 13 January 2017 at 11:20, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > On Fri, Jan 13, 2017 at 11:01:42AM -0800, Aliaksei Syrel wrote: > > Hi Peter, > > > > Latest windows VMs produce crash dumps ;) > > Excellent! :) > > Peter > > > > > Cheers, > > Alex > > > > On 13 January 2017 at 10:57, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > > On Fri, Jan 13, 2017 at 10:27:27AM -0800, Aliaksei Syrel wrote: > > > > Hi > > > > > > > > The following code crashes windows spur32 VM without crash.dmp: > > > > (crashes not only in case of int8, but ulong, int16/32 and so on...) > > > > > > I don't think that Windows produces crash dumps (or they are empty > files), > > > but maybe you can find some info in Event Viewer (start>run > "eventvwr.msc") > > > in Event Viewer > Windows Logs > Application. > > > > > > > > > > > Callback instantiation: > > > > > > > > createCallback > > > > > ^ FFICallback > > > > > signature: #(int8 (int8)) > > > > > block: [ :value | value ] > > > > > > > > > > > > C function: > > > > > > > > int8_t test(int8_t(*function)(int8_t), int8_t value) { > > > > > return function(value); > > > > > } > > > > > > > > > > > > FFI call: > > > > > > > > primCall: aCallback int8: aNumber > > > > > ^ self ffiCall: #(int8 test(FFICallback aCallback, int8 > aNumber)) > > > > > > > > > > > > Test case: > > > > > > > > test > > > > > self > > > > > assert: (self primCall: self createCallback int8: 0) > > > > > equals: 0 > > > > > > > > > > > > > > > > Windows 10. > > > > VM from today: > > > > http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > > > i386-201701130756-83c0ef1.zip > > > > Image 60343: > > > > http://files.pharo.org/image/60/60343.zip > > > > > > > > P.S. what is the best place to report FFI / Alien issues? > > > > P.P.S Iceberg works > > > > > > > > Cheers, > > > > Alex > > > > > > > >

Jan. 13, 2017

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

by Peter Uhnak

On Fri, Jan 13, 2017 at 11:01:42AM -0800, Aliaksei Syrel wrote: > Hi Peter, > > Latest windows VMs produce crash dumps ;) Excellent! :) Peter > > Cheers, > Alex > > On 13 January 2017 at 10:57, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > On Fri, Jan 13, 2017 at 10:27:27AM -0800, Aliaksei Syrel wrote: > > > Hi > > > > > > The following code crashes windows spur32 VM without crash.dmp: > > > (crashes not only in case of int8, but ulong, int16/32 and so on...) > > > > I don't think that Windows produces crash dumps (or they are empty files), > > but maybe you can find some info in Event Viewer (start>run "eventvwr.msc") > > in Event Viewer > Windows Logs > Application. > > > > > > > > Callback instantiation: > > > > > > createCallback > > > > ^ FFICallback > > > > signature: #(int8 (int8)) > > > > block: [ :value | value ] > > > > > > > > > C function: > > > > > > int8_t test(int8_t(*function)(int8_t), int8_t value) { > > > > return function(value); > > > > } > > > > > > > > > FFI call: > > > > > > primCall: aCallback int8: aNumber > > > > ^ self ffiCall: #(int8 test(FFICallback aCallback, int8 aNumber)) > > > > > > > > > Test case: > > > > > > test > > > > self > > > > assert: (self primCall: self createCallback int8: 0) > > > > equals: 0 > > > > > > > > > > > > Windows 10. > > > VM from today: > > > http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > > i386-201701130756-83c0ef1.zip > > > Image 60343: > > > http://files.pharo.org/image/60/60343.zip > > > > > > P.S. what is the best place to report FFI / Alien issues? > > > P.P.S Iceberg works > > > > > > Cheers, > > > Alex > > > >

Jan. 13, 2017

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

by Aliaksei Syrel

Hi Peter, Latest windows VMs produce crash dumps ;) Cheers, Alex On 13 January 2017 at 10:57, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > On Fri, Jan 13, 2017 at 10:27:27AM -0800, Aliaksei Syrel wrote: > > Hi > > > > The following code crashes windows spur32 VM without crash.dmp: > > (crashes not only in case of int8, but ulong, int16/32 and so on...) > > I don't think that Windows produces crash dumps (or they are empty files), > but maybe you can find some info in Event Viewer (start>run "eventvwr.msc") > in Event Viewer > Windows Logs > Application. > > > > > Callback instantiation: > > > > createCallback > > > ^ FFICallback > > > signature: #(int8 (int8)) > > > block: [ :value | value ] > > > > > > C function: > > > > int8_t test(int8_t(*function)(int8_t), int8_t value) { > > > return function(value); > > > } > > > > > > FFI call: > > > > primCall: aCallback int8: aNumber > > > ^ self ffiCall: #(int8 test(FFICallback aCallback, int8 aNumber)) > > > > > > Test case: > > > > test > > > self > > > assert: (self primCall: self createCallback int8: 0) > > > equals: 0 > > > > > > > > Windows 10. > > VM from today: > > http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > i386-201701130756-83c0ef1.zip > > Image 60343: > > http://files.pharo.org/image/60/60343.zip > > > > P.S. what is the best place to report FFI / Alien issues? > > P.P.S Iceberg works > > > > Cheers, > > Alex > >

Jan. 13, 2017

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

by Peter Uhnak

On Fri, Jan 13, 2017 at 10:27:27AM -0800, Aliaksei Syrel wrote: > Hi > > The following code crashes windows spur32 VM without crash.dmp: > (crashes not only in case of int8, but ulong, int16/32 and so on...) I don't think that Windows produces crash dumps (or they are empty files), but maybe you can find some info in Event Viewer (start>run "eventvwr.msc") in Event Viewer > Windows Logs > Application. > > Callback instantiation: > > createCallback > > ^ FFICallback > > signature: #(int8 (int8)) > > block: [ :value | value ] > > > C function: > > int8_t test(int8_t(*function)(int8_t), int8_t value) { > > return function(value); > > } > > > FFI call: > > primCall: aCallback int8: aNumber > > ^ self ffiCall: #(int8 test(FFICallback aCallback, int8 aNumber)) > > > Test case: > > test > > self > > assert: (self primCall: self createCallback int8: 0) > > equals: 0 > > > > Windows 10. > VM from today: > http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201701130756-83c0… > Image 60343: > http://files.pharo.org/image/60/60343.zip > > P.S. what is the best place to report FFI / Alien issues? > P.P.S Iceberg works > > Cheers, > Alex

Jan. 13, 2017