October 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Updated Pharo By Example

by Dimitris Chloupis

Hello Mariano, thank you for your kind word of course I am one of the many contributors and UPBE is a collective effort. We dont have an image right now for UPBE and I think that the best way to approach this is to make a package for the Catalog Browser . This means you will be able to use UPBE examples to any image you have instead of being isolated to a different image. When this will happen I cant promise anything since our first priority is to make the documentation as up to date as possible. Currently we support Pharo 4 and 5 , with focus of course on Pharo 5. Obviously in the future the focus will continuously shift towards the latest version. So when we put the "Updated" to Pharo by Example, we mean business. On Mon, Oct 26, 2015 at 6:04 PM Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi Dimitris, > > Thank you very much for your hard work. It was so much needed. In fact, I > need it now :) > I have question... remember the old PBE used to have a VM + image for the > book, which was the image expected to be used while reading the book. Is > there a new VM + image prepared for UPBE? If true, where? If not, then at > least which Pharo version is expected to be used as a reference? 4.0? > > Thanks in advance, > > > On Fri, Oct 23, 2015 at 4:19 PM, Stephan Eggermont <stephan(a)stack.nl> > wrote: > >> On 23-10-15 19:15, Thierry Goubier wrote: >> >>> Le 23 oct. 2015 7:00 PM, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a >>> Ã©crit : >>> >>>> >>>> I completely agree with Stef, I did actually removed some screenshots >>>> and >>>> >>> someone put them pack >>> >>>> >>>> Maybe I can create a pharo script to auto make them for each version >>>> >>> >>> Wasn't there a way to run Smalltalk code inside pillar? Code that would >>> open windows, screenshot and return a png. >>> >> >> Well, there is Documentation-Screenshots in StephanEggermont/Documentation >> >> You create a DOScreenshotExporter, set its directory and tell it which >> forms/morphs/nautilus/world you want stored there under which filename. >> I fixed a few remaining bugs today. >> >> I presume you should be able to use it in pillar. >> >> You can use it like >> >> so := DOScreenshotExporter new. >> so directory: FileLocator home. >> so writeNautilusMethod: DOScreenshotExporter>>#directory: as: >> 'directoryMethod.png' >> >> It has methods like >> DOScreenshotExporter>>writeNautilusMethod: aMethod as: aFileName >> self writeBlock: [(Nautilus openOnMethod: aMethod) ui window imageForm >> ] as: aFileName >> >> This makes sure to first rename an existing file before overwriting it. >> >> DOScreenshotExporter>>writeBlock: aBlock as: aFileName >> |temp| >> (directory / aFileName) exists ifTrue: [ >> temp := (directory / aFileName) renameTo: (aFileName,'tmp') ]. >> PNGReadWriter putForm: aBlock value onFileNamed: (directory / >> aFileName). >> temp ifNotNil: [ temp ensureDelete ] >> >> Stephan >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com >

Oct. 26, 2015

Re: [Pharo-users] Pharo family update

by Martin BÃ¤hr

Excerpts from Adam's message of 2015-10-26 01:23:09 +0100: > Pharo is mostly development platform, and image shows mostly libraries and > frameworks for development, but "Development" circle in the image is more > about tools primarly targeted to support process of development. So, if Gofer > and Metacello is not used for this purpose (maybe it is, I'm not sure), it > should be in "Working" circle. thanks for clarifying that. now i understand the difference. of course they are related, but one is used by people who want to install software, while the other is used by developers managing their cod i wonder if "development" could have a better name, like "tools" or "development tools" and if most things are about development, then "web development" might be "web frameworks" or just "web" because otherwise it gives the impression that other things would not be about development. one more thing, i find the grey-on-white small text hard to read. i have to zoom in a lot to make it out. small text like that would be better with higher contrast. svg apparently supports tooltips: http://stackoverflow.com/questions/102457/how-to-create-an-svg-tooltip-like… maybe that can be used here. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Oct. 26, 2015

Re: [Pharo-users] Updated Pharo By Example

by Mariano Martinez Peck

Hi Dimitris, Thank you very much for your hard work. It was so much needed. In fact, I need it now :) I have question... remember the old PBE used to have a VM + image for the book, which was the image expected to be used while reading the book. Is there a new VM + image prepared for UPBE? If true, where? If not, then at least which Pharo version is expected to be used as a reference? 4.0? Thanks in advance, On Fri, Oct 23, 2015 at 4:19 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 23-10-15 19:15, Thierry Goubier wrote: > >> Le 23 oct. 2015 7:00 PM, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a >> Ã©crit : >> >>> >>> I completely agree with Stef, I did actually removed some screenshots and >>> >> someone put them pack >> >>> >>> Maybe I can create a pharo script to auto make them for each version >>> >> >> Wasn't there a way to run Smalltalk code inside pillar? Code that would >> open windows, screenshot and return a png. >> > > Well, there is Documentation-Screenshots in StephanEggermont/Documentation > > You create a DOScreenshotExporter, set its directory and tell it which > forms/morphs/nautilus/world you want stored there under which filename. > I fixed a few remaining bugs today. > > I presume you should be able to use it in pillar. > > You can use it like > > so := DOScreenshotExporter new. > so directory: FileLocator home. > so writeNautilusMethod: DOScreenshotExporter>>#directory: as: > 'directoryMethod.png' > > It has methods like > DOScreenshotExporter>>writeNautilusMethod: aMethod as: aFileName > self writeBlock: [(Nautilus openOnMethod: aMethod) ui window imageForm ] > as: aFileName > > This makes sure to first rename an existing file before overwriting it. > > DOScreenshotExporter>>writeBlock: aBlock as: aFileName > |temp| > (directory / aFileName) exists ifTrue: [ > temp := (directory / aFileName) renameTo: (aFileName,'tmp') ]. > PNGReadWriter putForm: aBlock value onFileNamed: (directory / aFileName). > temp ifNotNil: [ temp ensureDelete ] > > Stephan > > > -- Mariano http://marianopeck.wordpress.com

Oct. 26, 2015

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

by Attila Magyar

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.3… Attila -- View this message in context: http://forum.world.st/ANN-Working-with-Pharo-on-the-Raspberry-Pi-tp4857895p… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 26, 2015

Re: [Pharo-users] Problem to connect Seaside and Pharo

by Justine STIENNE

Thank you for your help. You're right, I'm mixing instance and class side, I will revise it. I'm following the standard Pharo book. Justine 2015-10-26 9:31 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 26 Oct 2015, at 09:09, Justine STIENNE <justine.stienne(a)gmail.com> > wrote: > > > > Of course. Sorry to bother you but I'm a beginner. > > OK, no problem. > > You are mixing instance and class side. All your methods except > #renderContentOn: should be on the class side. There should also be no > super initialise on the class side. > > What book/tutorial are you following ? > > Standard Pharo books are at http://books.pharo.org > > You should make sure that you read and experiment with the first one. > > There is also the Seaside book. > > The learning curve in the beginning can be quite steep, depending on your > background, nothing to worry about. > > > 2015-10-26 9:01 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > Could you do a File Out of your WAHelloWorld class code and show us ? > > > > > On 26 Oct 2015, at 08:58, Justine STIENNE <justine.stienne(a)gmail.com> > wrote: > > > > > > I have just done it. And now, on 'http://localhost:8080/config/hello' > , I can choose 'a WAHelloWorld', but not 'WAHelloWorld'. > > > When I go to 'http://localhost:8080/hello', I have : > > > MessageNotUnderstood: WAHelloWorld>>new > > > > > > Your request could not be completed. An exception occurred. > > > > > > > > > > > > Thanks in advance, > > > > > > Justine > > > > > > > > > > > > 2015-10-25 20:03 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > You have to do (Do it) the #initialize as well, like > > > > > > MyExample initialize. > > > > > > Or browse the method and highlight the body and evaluate it (Do it). > > > > > > > On 25 Oct 2015, at 20:00, Justine STIENNE <justine.stienne(a)gmail.com> > wrote: > > > > > > > > Oh sorry it was not for this conversation. I tried to do what you > said, but it doesn't work again. > > > > > > > > Justine > > > > > > > > 2015-10-25 19:55 GMT+01:00 Justine STIENNE < > justine.stienne(a)gmail.com>: > > > > The installation is ok ! :-) But i cant open the file bak that you > give me :-/ > > > > > > > > 2015-10-25 18:53 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > Hi, > > > > > > > > > On 25 Oct 2015, at 18:46, Justine STIENNE < > justine.stienne(a)gmail.com> wrote: > > > > > > > > > > Hello, > > > > > > > > > > I have a problem to connect Seaside and Pharo. I explain : > > > > > > > > > > ZnZincServerAdaptor is running. When I open localhost:8080, it > works. When I want to configure a new entry, I can't find the class that I > made on Pharo. I have put the method canBeRoot with true as return value on > a class but I can't find it. Can you help me ? > > > > > > > > > > Thanks in advance, > > > > > Justine > > > > > > > > #canBeRoot is just an indication, it has no real effect on its own. > > > > > > > > Traditionally, WAComponent subclasses register themselves explicitly > using #initialize on the class side, like this: > > > > > > > > initialize > > > > WAAdmin register: self asApplicationAt: self handlerName > > > > > > > > Look for the senders of #register:asApplicationAt: to see what I > mean. > > > > > > > > Sven > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <WAHelloWorld.st> > > >

Oct. 26, 2015

Re: [Pharo-users] Pharo family update

by HernÃ¡n Morales Durand

2015-10-26 11:08 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > Thanks Adam. This is a great initiative. I really like the > internal/external distinction. > > A few questions... > > Why is "Compilers" outside the circle? > > What is the "VB" part of "VB-Regex" ? > > Vassili Bykov was the original author of Regex11 and later it was renamed. > and a few suggestions... > > > About categories I would group in different way but it's personal > choice. Like... > > Reflection > > It would be nice to emphasise our reflective capability, but what > would be some subparts? > > Reflection is commonly decomposed in two parts: Introspection and intercession. > > Code Analysis > > This could just be "Analysis" and include Moose and SciSmalltalk. > > > Persistency > > Maybe "Connectors" could be renamed to "Persistence". > > Yes, besides that would avoid confusion with the Connectors package. > It would be good to promote in-Image persistence solutions since that > is a speed advantage for prototyping. btw, Is SimplePersistance > stable enough to be included? > http://smalltalkhub.com/#!/~TorstenBergmann/SimplePersistence > > I don't know about SimplePersistence but in-image persistence is a cool feature that other technologies lack. > I don't think Magma and SandstoneDb provide services to other clients > (??) and so don't seem related to "Server" and would group better with > "Connectors/Persistence". That does then leave "Server" a bit bare. > Perhaps "RemoteFrameBuffer" would be a good fit. > > > "Output" is a bit too much like "Export". Perhaps it could be renamed > "Presentation" > > The legend could be moved to a corner (bottom left?), and "Pharo" > could be moved more centrally to its place. In another shaded corner > you might list the major repositories: > * smalltalkhub.com > * ss3.gemtalksystems.com > * squeaksource.com > Anyone with further ideas for the other two corners? > > I'm not sure that "Define" is the right tag for "Magritte". I think > its an implementation of the "Momento" pattern, so maybe that would be > better (or maybe that is too exotic?). Would it be reasonable to tag > it s "Forms" (??) > > That would require multi-class multi-label classification, because Magritte (and other packages) cover many areas. > "Fuel" would seem to go better near STON/JSON on "Import/Export". > > As well as "SUnit" as a framework, "Testing" should have "TestRunner" > and a tool. > > Agree, the TestRunner is important. > "Searching > Spotter" would go well up next to "Finder" > > "Monticello" should go closer to "Metacello" and is perhaps a good fit > to move it down to "Working", and also Versioneer is closely related > to "Metacello". "Metacello" and "CatalogBrowser" would do well to > be tagged together as "Deployment" > > I like that you've got "Computations" with SciSmalltalk and > BioSmalltalk, but actually it might be good to repurpose this > "Downstream Distributions". I think such a section demostrates a > level of maturity of a system, which is important to show. This might > then also include Moose, Phratch, Dr.Geo and PharoROS(?). Chalten and > Aconcagua might be re-homed under "Data." > > Yes, I suspect it could be solved with multi-class multi-label tags. > "Spec" and "Athens" are internal to Pharo. > > I don't see why internal? Does that mean it wouldn''t be ported to other ST flavors? > whoops. thats a lot. Some parts I'm not sure on - wait and see what > others think. > cheers -ben > > Really nice diagram, but it needs more promoting outside the Smalltalk circle. HernÃ¡n > > On Sat, Oct 24, 2015 at 7:30 PM, Ferlicot D. Cyril > <cyril.ferlicot(a)gmail.com> wrote: > > Le 24/10/2015 09:27, stepharo a Ã©crit : > >> Superb! Really nice > >> Margritte -> Magritte > >> Mondorian -> Mondrian > >> > >> to add > >> > >> Never heard about PharoLink but you should have Garage (a database > >> generic API) > >> > >> You could add MongoTalk close to Voyage > >> > >> GLORP > >> Relational > >> Mapper > >> > >> Woden 3D > >> Roassal3D > >> > >> Omnibrowser is deprecated > >> > >> I would put STON close to Fuel > >> May be you should move closer the two spots: import/export and data > >> > >> Tide is not developed anymore so I would remove it > >> Add Reef instead (Javascript-enabled Web components) > >> > >> About Graphics > >> > >> you should have > >> Athens (Vector graphics API) > >> Bloc (new generation Morphic) > >> Brick (new generation widgets) > >> > >> > > > > Hi, > > > > I do not agree to add Reef, Bloc and Brick now if this map is for > beginners. > > If this map is for beginners that need a framework we should wait to > > have a usable version with documentation. > > I think Bloc and Brick are not finish yet (I think) and reef lack > > documentation/tutorial. > > > > If a beginner see it on the map and test it he will have a bad first > > impression. And first impression count. > > > > This project should be on a waiting list the time there are stable and > > documented I think. But this is just my opinion. > > > > -- > > Cyril Ferlicot > > > > http://www.synectique.eu > > > > 165 Avenue Bretagne > > Lille 59000 France > > > >

Oct. 26, 2015

Objects on demand for big collections

by Oswall Verny Arguedas C.

It will be possible to load objects on demand (for a list or html table) to avoid unnecessary objects and load ?.To page sending large lists of objects from the server to the client. I use Pharo 4 and Seaside 3.2 on linux ubuntu. ThanksOswall

Oct. 26, 2015

Re: [Pharo-users] Pharo family update

by Ben Coman

Thanks Adam. This is a great initiative. I really like the internal/external distinction. A few questions... Why is "Compilers" outside the circle? What is the "VB" part of "VB-Regex" ? and a few suggestions... > About categories I would group in different way but it's personal choice. Like... > Reflection It would be nice to emphasise our reflective capability, but what would be some subparts? > Code Analysis This could just be "Analysis" and include Moose and SciSmalltalk. > Persistency Maybe "Connectors" could be renamed to "Persistence". It would be good to promote in-Image persistence solutions since that is a speed advantage for prototyping. btw, Is SimplePersistance stable enough to be included? http://smalltalkhub.com/#!/~TorstenBergmann/SimplePersistence I don't think Magma and SandstoneDb provide services to other clients (??) and so don't seem related to "Server" and would group better with "Connectors/Persistence". That does then leave "Server" a bit bare. Perhaps "RemoteFrameBuffer" would be a good fit. "Output" is a bit too much like "Export". Perhaps it could be renamed "Presentation" The legend could be moved to a corner (bottom left?), and "Pharo" could be moved more centrally to its place. In another shaded corner you might list the major repositories: * smalltalkhub.com * ss3.gemtalksystems.com * squeaksource.com Anyone with further ideas for the other two corners? I'm not sure that "Define" is the right tag for "Magritte". I think its an implementation of the "Momento" pattern, so maybe that would be better (or maybe that is too exotic?). Would it be reasonable to tag it s "Forms" (??) "Fuel" would seem to go better near STON/JSON on "Import/Export". As well as "SUnit" as a framework, "Testing" should have "TestRunner" and a tool. "Searching > Spotter" would go well up next to "Finder" "Monticello" should go closer to "Metacello" and is perhaps a good fit to move it down to "Working", and also Versioneer is closely related to "Metacello". "Metacello" and "CatalogBrowser" would do well to be tagged together as "Deployment" I like that you've got "Computations" with SciSmalltalk and BioSmalltalk, but actually it might be good to repurpose this "Downstream Distributions". I think such a section demostrates a level of maturity of a system, which is important to show. This might then also include Moose, Phratch, Dr.Geo and PharoROS(?). Chalten and Aconcagua might be re-homed under "Data." "Spec" and "Athens" are internal to Pharo. whoops. thats a lot. Some parts I'm not sure on - wait and see what others think. cheers -ben On Sat, Oct 24, 2015 at 7:30 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > Le 24/10/2015 09:27, stepharo a Ã©crit : >> Superb! Really nice >> Margritte -> Magritte >> Mondorian -> Mondrian >> >> to add >> >> Never heard about PharoLink but you should have Garage (a database >> generic API) >> >> You could add MongoTalk close to Voyage >> >> GLORP >> Relational >> Mapper >> >> Woden 3D >> Roassal3D >> >> Omnibrowser is deprecated >> >> I would put STON close to Fuel >> May be you should move closer the two spots: import/export and data >> >> Tide is not developed anymore so I would remove it >> Add Reef instead (Javascript-enabled Web components) >> >> About Graphics >> >> you should have >> Athens (Vector graphics API) >> Bloc (new generation Morphic) >> Brick (new generation widgets) >> >> > > Hi, > > I do not agree to add Reef, Bloc and Brick now if this map is for beginners. > If this map is for beginners that need a framework we should wait to > have a usable version with documentation. > I think Bloc and Brick are not finish yet (I think) and reef lack > documentation/tutorial. > > If a beginner see it on the map and test it he will have a bad first > impression. And first impression count. > > This project should be on a waiting list the time there are stable and > documented I think. But this is just my opinion. > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France >

Oct. 26, 2015

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

by 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 <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. > On Oct 24, 2015, at 19:45, Nicolai Hess <nicolaihess(a)gmail.com> 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 <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>: > > 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 <btc(a)openInWorld.com> wrote: > > > > On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> 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 <http://tinyurl.com/gdb-trace-all> > > > > > > ---> 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 > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Oct. 26, 2015

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

by Johan Fabry

Hi Robert, thanks for the hints. Unfortunately running in Pharo 5 is not feasible. PhaROS does not do any low-level calls as far as I am aware (I did not implement it, Iâm just using it). I will try to run it in gdb as soon as I can find a reliable way to reproduce the crash. > On Oct 24, 2015, at 16:52, Robert Withers <robert.w.withers(a)gmail.com> wrote: > > Posting to Pharos-dev or Vm Dev may find you more assistance. > > My suggestions would be: a) upgrade to Pharo 5 and b) run in gdb so we all can be better informed about the issue you are seeing. Is PhaROS doing low level calls? > > --- > robert > >> On Oct 24, 2015, at 3:32 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: >> >> >> 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 <btc(a)openInWorld.com> wrote: >>> >>> On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry(a)dcc.uchile.cl> 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 >> >> > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Oct. 26, 2015