December 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About loading PetitParser into Pharo 5?

by Stephan Eggermont

On 31/12/15 10:25, H. Hirzel wrote: > Hello > > PetitParser (in Catalog) does not load yet in Pharo 5. It is tagged > with 'Pharo 4'. > > The feedback message is that the installation was aborted. > > Where can I check why it has been aborted? Hi Hannes, I copied a newer version of the configuration to the Pharo4 and 5 metarepos. The last one there was 61 from March 16. Stephan

Dec. 31, 2015

Re: [Pharo-dev] [Moose-dev] Roassal2 in Pharo 5 -> segfault

by Nicolai Hess

2015-12-31 10:09 GMT+01:00 stepharo <stepharo(a)free.fr>: > Hi nicolai > > > The same on windows. Every RoassalExample crashes immeditly. >> Simple Trachel examples are working (TRCanvasExample>>circle) >> but as soon as some text is drawn (TRCanvasExample>>label) >> the vm crashes. >> >> For example, in >> CairoFreeTypeFontRenderer>>#glyphsOf: aString from: start to: end >> at: >> self freeGlyphs: ptr. >> >> If I remove this line, or replace it with >> ptr free. >> The VM crashes at some >> primitiveFFIAllocate call >> >> But I don't understand the whole implementation behind the new FFI (don't >> understand what are the difference between #getHandle, #pointer, >> #gcpointer, ... what memory >> is garbage collected,. what not or when the memory should be freed by >> cairos api (like void cairo_glyph_free (void *glyphs)). >> > Thanks for asking. > Esteban should document all that. > I think that we need more people looking at it and pushing the > documentation. > I don't understand why this is working on Linux, but not on windows. Any hints where the FFI implementation depends on differences between windows and linux? > > Stef > >

Dec. 31, 2015

Re: [Pharo-dev] [Moose-dev] Roassal2 in Pharo 5 -> segfault

by Alexandre Bergel

ok cool! Alexandre > On Dec 31, 2015, at 6:10 AM, stepharo <stepharo(a)free.fr> wrote: > > > > Le 30/12/15 19:03, Alexandre Bergel a Ã©crit : >> Esteban, do you have a bit of documentation? > > it is on the way. Esteban started to sketch an online when we were in Togo and I think that FFI will be the > item number one of Esteban for the coming weeks. > > stef >> The OpenGL bindings will have to be migrated. It would be great to have a starting point. >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Dec 30, 2015, at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> Hi, >>> >>> Iâve seen this aroundâ¦ I think is because a problem copying memoryâ¦ I will check it (next week, Iâm on holidays now) but I would like to have a bug report, please. >>> >>> btwâ¦ the crashes are not related to Spur but the new FFI implementation (and the migration from old NativeBoost). Spur itself is pretty stable :) >>> >>> Esteban >>> >>>> On 29 Dec 2015, at 19:59, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> >>>> I have also seen some random crashes using Spurâ¦ >>>> >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>>> On Dec 29, 2015, at 2:33 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> just in case this is not a known bug: Intensive use of Roassal2 in Pharo 5 causes a segfault of the mac vm. A crash.dump is attached. Itâs the vm I got just now ( wget --quiet -O - get.pharo.org/50+vm | bash ) and Pharo5 with Alexesâ 17280 slice to make Roassal visualize shapes correctly. >>>>> >>>>> To reproduce, all I need to do is have a visualization open with a layout animation and after some time it will crash. I use this in LRP and I can give easy steps to reproduce if needed. >>>>> >>>>> <crash.dmp> >>>>> >>>>> ---> Save our in-boxes! http://emailcharter.org <--- >>>>> >>>>> Johan Fabry - http://pleiad.cl/~jfabry >>>>> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)list.inf.unibe.ch >>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 31, 2015

About loading PetitParser into Pharo 5?

by H. Hirzel

Hello PetitParser (in Catalog) does not load yet in Pharo 5. It is tagged with 'Pharo 4'. The feedback message is that the installation was aborted. Where can I check why it has been aborted? Kind regards Hannes

Dec. 31, 2015

Re: [Pharo-dev] [Moose-dev] Roassal2 in Pharo 5 -> segfault

by stepharo

Le 30/12/15 19:03, Alexandre Bergel a Ã©crit : > Esteban, do you have a bit of documentation? it is on the way. Esteban started to sketch an online when we were in Togo and I think that FFI will be the item number one of Esteban for the coming weeks. stef > The OpenGL bindings will have to be migrated. It would be great to > have a starting point. > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Dec 30, 2015, at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com >> <mailto:estebanlm@gmail.com>> wrote: >> >> Hi, >> >> Iâve seen this aroundâ¦ I think is because a problem copying memoryâ¦ I >> will check it (next week, Iâm on holidays now) but I would like to >> have a bug report, please. >> >> btwâ¦ the crashes are not related to Spur but the new FFI >> implementation (and the migration from old NativeBoost). Spur itself >> is pretty stable :) >> >> Esteban >> >>> On 29 Dec 2015, at 19:59, Alexandre Bergel <alexandre.bergel(a)me.com >>> <mailto:alexandre.bergel@me.com>> wrote: >>> >>> I have also seen some random crashes using Spurâ¦ >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On Dec 29, 2015, at 2:33 PM, Johan Fabry <jfabry(a)dcc.uchile.cl >>>> <mailto:jfabry@dcc.uchile.cl>> wrote: >>>> >>>> Hi all, >>>> >>>> just in case this is not a known bug: Intensive use of Roassal2 in >>>> Pharo 5 causes a segfault of the mac vm. A crash.dump is attached. >>>> Itâs the vm I got just now ( wget --quiet -O - get.pharo.org/50+vm >>>> <http://get.pharo.org/50+vm> | bash ) and Pharo5 with Alexesâ 17280 >>>> slice to make Roassal visualize shapes correctly. >>>> >>>> To reproduce, all I need to do is have a visualization open with a >>>> layout animation and after some time it will crash. I use this in >>>> LRP and I can give easy steps to reproduce if needed. >>>> >>>> <crash.dmp> >>>> >>>> ---> Save our in-boxes! http://emailcharter.org >>>> <http://emailcharter.org/> <--- >>>> >>>> Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> >>>> PLEIAD and RyCh labs - Computer Science Department (DCC) - >>>> University of Chile >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >> https://www.list.inf.unibe.ch/listinfo/moose-dev >

Dec. 31, 2015

Re: [Pharo-dev] [Moose-dev] Roassal2 in Pharo 5 -> segfault

by stepharo

Hi nicolai > The same on windows. Every RoassalExample crashes immeditly. > Simple Trachel examples are working (TRCanvasExample>>circle) > but as soon as some text is drawn (TRCanvasExample>>label) > the vm crashes. > > For example, in > CairoFreeTypeFontRenderer>>#glyphsOf: aString from: start to: end > at: > self freeGlyphs: ptr. > > If I remove this line, or replace it with > ptr free. > The VM crashes at some > primitiveFFIAllocate call > > But I don't understand the whole implementation behind the new FFI > (don't understand what are the difference between #getHandle, > #pointer, #gcpointer, ... what memory > is garbage collected,. what not or when the memory should be freed by > cairos api (like void cairo_glyph_free (void *glyphs)). Thanks for asking. Esteban should document all that. I think that we need more people looking at it and pushing the documentation. Stef

Dec. 31, 2015

Re: [Pharo-dev] Small pillar question

by stepharo

may be == \=\= == Le 30/12/15 16:17, Alexandre Bergel a Ã©crit : > Hi! > > How can I write == in a code format? > == == == obviously does not parse wellâ¦ > > Any alternative? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Dec. 31, 2015

Re: [Pharo-dev] [Moose-dev] Roassal2 in Pharo 5 -> segfault

by Nicolai Hess

2015-12-30 19:03 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Esteban, do you have a bit of documentation? The OpenGL bindings will have > to be migrated. It would be great to have a starting point. > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Dec 30, 2015, at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > Hi, > > Iâve seen this aroundâ¦ I think is because a problem copying memoryâ¦ I will > check it (next week, Iâm on holidays now) but I would like to have a bug > report, please. > > btwâ¦ the crashes are not related to Spur but the new FFI implementation > (and the migration from old NativeBoost). Spur itself is pretty stable :) > > Esteban > > The same on windows. Every RoassalExample crashes immeditly. Simple Trachel examples are working (TRCanvasExample>>circle) but as soon as some text is drawn (TRCanvasExample>>label) the vm crashes. For example, in CairoFreeTypeFontRenderer>>#glyphsOf: aString from: start to: end at: self freeGlyphs: ptr. If I remove this line, or replace it with ptr free. The VM crashes at some primitiveFFIAllocate call But I don't understand the whole implementation behind the new FFI (don't understand what are the difference between #getHandle, #pointer, #gcpointer, ... what memory is garbage collected,. what not or when the memory should be freed by cairos api (like void cairo_glyph_free (void *glyphs)). > > On 29 Dec 2015, at 19:59, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > I have also seen some random crashes using Spurâ¦ > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Dec 29, 2015, at 2:33 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Hi all, > > just in case this is not a known bug: Intensive use of Roassal2 in Pharo 5 > causes a segfault of the mac vm. A crash.dump is attached. Itâs the vm I > got just now ( wget --quiet -O - get.pharo.org/50+vm | bash ) and Pharo5 > with Alexesâ 17280 slice to make Roassal visualize shapes correctly. > > To reproduce, all I need to do is have a visualization open with a layout > animation and after some time it will crash. I use this in LRP and I can > give easy steps to reproduce if needed. > > <crash.dmp> > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > >

Dec. 30, 2015

Re: [Pharo-dev] Small pillar question

by Alexandre Bergel

Cool! It works!!! cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Dec 30, 2015, at 12:29 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Le 30/12/2015 16:17, Alexandre Bergel a Ã©crit : >> Hi! >> >> How can I write == in a code format? >> == == == obviously does not parse wellâ¦ >> >> Any alternative? > > Hi, > > ==\=\=== > >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > > > -- > Cyril Ferlicot > > http://www.synectique.eu <http://www.synectique.eu/> > > 165 Avenue Bretagne > Lille 59000 France

Dec. 30, 2015

Re: [Pharo-dev] [Moose-dev] Roassal2 in Pharo 5 -> segfault

by Alexandre Bergel

Esteban, do you have a bit of documentation? The OpenGL bindings will have to be migrated. It would be great to have a starting point. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Dec 30, 2015, at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Iâve seen this aroundâ¦ I think is because a problem copying memoryâ¦ I will check it (next week, Iâm on holidays now) but I would like to have a bug report, please. > > btwâ¦ the crashes are not related to Spur but the new FFI implementation (and the migration from old NativeBoost). Spur itself is pretty stable :) > > Esteban > >> On 29 Dec 2015, at 19:59, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> I have also seen some random crashes using Spurâ¦ >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Dec 29, 2015, at 2:33 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: >>> >>> Hi all, >>> >>> just in case this is not a known bug: Intensive use of Roassal2 in Pharo 5 causes a segfault of the mac vm. A crash.dump is attached. Itâs the vm I got just now ( wget --quiet -O - get.pharo.org/50+vm <http://get.pharo.org/50+vm> | bash ) and Pharo5 with Alexesâ 17280 slice to make Roassal visualize shapes correctly. >>> >>> To reproduce, all I need to do is have a visualization open with a layout animation and after some time it will crash. I use this in LRP and I can give easy steps to reproduce if needed. >>> >>> <crash.dmp> >>> >>> ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- >>> >>> Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> >>> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >>> https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Dec. 30, 2015