VM-beginners November 2011

vm-beginners@lists.squeakfoundation.org

2 participants
7 discussions

Fwd: Oops - I put a halt in a startup method
by Sean P. DeNigris 10 Jan '12

10 Jan '12

From http://forum.world.st/Oops-I-put-a-halt-in-a-startup-method-td3800163.html : My image appears for an instant and then crashes. Is there any way to recover from this? I made some progress, but I'm not sure I'm on the right track... I built a debug VM and found primitivePerform, which is apparently called by the following: FeaturesDB perform: #startUp: with: resuming How will I know which call to skip/break on? Maybe there is there a way, from the VM side, to get the receiver class name as a string? If I knew that the receiver was FeaturesDB, that would be the one... And then once I have the right call, can I just skip over it? Sean -- View this message in context: http://forum.world.st/Fwd-Oops-I-put-a-halt-in-a-startup-method-tp3800729p3… Sent from the Smalltalk VM - Beginners mailing list archive at Nabble.com.

4 15

Got "Error: basicNew: failed" when running InterpreterSimulator
by Nick. 21 Dec '11

21 Dec '11

Hi guys! In the past few days i tried to get InterpreterSimulator running without success. First of all, a little context about my goal: I'm digging into the VM because i would like to be able to delegate to some class (that I'll develop) the responsibility for, say, the method lookup algorithm. With that in mind, here's what i've been doing: Using the Pharo 1.2 image Mariano Peck's prepared in his exellent article (http://marianopeck.wordpress.com/2011/04/23/how-to-debug-the-vm/), loaded the VMMaker package with the following script: Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfCog'; load. (Smalltalk at: #ConfigurationOfCog) project latestVersion load. Once it finishes (without errors) I "Save As" the current image as "demo.image", close it and open the original Pharo 1.2 image that Mariano provided. When, for example, I run: (CogVMSimulator new openOn: 'demo.image') test or (InterpreterSimulatorLSB new openOn: 'demo.image') test I get the following error: "Error: basicNew: failed" (see attached images at the end). When I tried to load VMMaker in the Pharo 1.3 OneClick release, I got another error (see attached images at the end). Am I doing something wrong? Are those the right simulators to use? I can tell the difference between all that are available in VMMaker package. Thanks in advance! Nick http://forum.world.st/file/n3835723/error_while_trying_to_run_InterpreterSi… http://forum.world.st/file/n3835723/Error_while_loading_VMMaker_in_Pharo-1.… -- View this message in context: http://forum.world.st/Got-Error-basicNew-failed-when-running-InterpreterSim… Sent from the Smalltalk VM - Beginners mailing list archive at Nabble.com.

2 9

Handling function keys in unix
by Guillermo Polito 22 Nov '11

22 Nov '11

So far, what I've learnt/found :). 1) I assume my build is using X11-display, since my keyboard events are generated there :P. 2) The X11 keyboard events are adapted to sq events in sqUnixX11.c >> x2sqKeyPlain 3) This build uses XLookupString, which brings char codes in Latin 1 instead of UTF-8. But X11 seems to support UTF-8 :/. 4) When pressing a function key, XLookupString does not fill the buffer with chars... and the KeySym is not handled. I added a line like case XK_F1: return 50; and Character class>>F1 ^ self value: 50 to test, and It works :). But I'm not sure which code is better to be returned yet :P. 5) My image now handles the F1, but only the keyDown and keyUp, since in sqUnixX11.c >> handleEvent I have something like: if (ucs4) /* only generate a key char event if there's a code. */ recordKeyboardEvent(keyCode, EventKeyChar, modifierState, ucs4); 6) I tried commenting the if, but that generates some garbage in my image when pressing Alt, Shift, Control... So, some questions I have at this point: - Which are the restrictions on the codes returned on translateCode (point 4) ? Are they ascii characters? In the image I see the value is the keychar + the modifiers encoded - Based on the prior question, Which codes should be assigned to function keys? - I don't fully understand yet what a ucs4 code is, but the keysyms are translated to them in sqUnixX11.c >> xkeysym2ucs4 which looks pretty magical :). Does someone know how this works? The comments are not really helpful :(. Thanks! Guille, vming :)

1 0

Re: [Vm-dev] How to build a standard Unix interpreter VM on Linux using a Squeak trunk image
by David T. Lewis 21 Nov '11

21 Nov '11

On Sun, Nov 20, 2011 at 10:25:30PM -0800, Markus Lampert wrote: > > Hi David, > > thanks for the tutorial, love it! > > One question though, when it comes to generating the sources I run into several warnings: > CrLfFileStream class>>new has been deprecated. This class is now obsolete, use MultiByteFileStream instead. > > > Is this expected? Yes, you will see this warning message if you have the showDeprecationWarnings preference enabled (the preference was not enabled in the image that I used, and I did not notice this). The warning is annoying but harmless. A fix is available (Eliot Miranda fixed in in the oscog branch), but I apparently neglected to commit it to the VMMaker repository. I'll fix it soon, thanks for pointing out the problem. Dave

1 0

How to build a standard Unix interpreter VM on Linux using a Squeak trunk image
by David T. Lewis 19 Nov '11

19 Nov '11

This is a topic that deserves an occasional update, so here is an updated step-by-step recipe for building with Squeak on Linux. These instructions are saved on the swiki at <http://wiki.squeak.org/squeak/6177> Start with a fresh image such as http://ftp.squeak.org/4.3alpha/Squeak4.3gamma-11793.zip (any recent Squeak image will do). Open a new Morphic project in which to work, and enter the project. Open a new workspace for taking notes as you work, and a transcript to display any transcript output that might appear. Open a Monticello browser. In the Monticello browser, add a new repository (+Repository button). Select "HTTP" repository type, and edit the repository information as follows: MCHttpRepository location: 'http://www.squeaksource.com/VMMaker' user: '' password: '' Open the new repository (select the new entry and click the Open button to get a new repository browser). In the repository browser, select category "update" from the list in the left panel, and select the top entry in the right panel (update-dtl.9.mcm as of this writing). Click the "Load" button to load VMMaker. This will load VMMaker and various related packages and plugins. This will load a base version of these packages (but you do not yet have the latest updates, see the next step below). You can see a version identification for your VMMaker package by evaluating "VMMaker versionString" in your workspace: VMMaker versionString ==> '4.7.9' In the workspace, evaluate the expression "VMMaker updateFromServer". This will update VMMaker and the other packages to the most up to date versions. During the merge process, a merge browser will open with a label such as "Merging FFI-Pools-eem.3". Highlight the entries and click "Keep", then click the "Merge" button to accept the merge and proceed (this merge conflict will not effect your VM, so it is safe to ignore it and proceed). When the update process is complete, you will have the latest VMMaker version: VMMaker versionString ==> '4.7.14' Save your image. Your image is now prepared for VM code generation, so the next steps will be to load the platform source code that is required for code generation and VM building. In a Linux terminal window (outside of Squeak), change your directory to your working Squeak directory (the same directory that you are using to run your image. lewis@linux-jh8m:~> cd squeak/Squeak4.3 lewis@linux-jh8m:~/squeak/Squeak4.3> Check out an up to date copy of the platforms source code. You will need to have Subversion installed on your Linux system: lewis@linux-jh8m:~/squeak/Squeak4.3> svn co http://squeakvm.org/svn/squeak/trunk <lots of messages snipped> Checked out revision 2515. lewis@linux-jh8m:~/squeak/Squeak4.3> svn co http://squeakvm.org/svn/squeak/trunk This will place all of the platform sources in a subdirectory called trunk/platforms. It is easier for VMMaker to find this directory if the platforms directory is in directly in your Squeak directory, so use a symbolic link to make it so: lewis@linux-jh8m:~/squeak/Squeak4.3> ln -s trunk/platforms platforms The platforms sources are now ready for use, so return to your Squeak image to generate your VM source code. Open a VMMaker tool withy world menu -> open... -> VMMaker Click the Help button and have a quick look at the help information. You can come back to it later to read in more detail. A list of available plugins appears in the left panel ("Plugins not built"). You can drag entiries from this panel into the "Internal Plugins" panel or the "External Plugins" panel, or you can right click on the panel and use the menu to copy all plugins from one panel to another (plugins that cannot be built on your platform will remain in the "Plugins not built" panel). We are building our first VM, so we will select just a few important plugins to build and omit many others for now. After you are confident that you can build a VM, you can add other plugins and any operating system libraries that may be needed to support them. You can also use a VMMaker configuration file to load a saved configuration, but for now we will do the work by hand to show how it is done. Use the mouse to drag and drop the following plugin entries from the "Plugins not built" panel to the "Internal plugins" panel. BalloonEnginePlugin BitBltSimulation DeflatePlugin FilePlugin LargeIntegersPlugin LocalePlugin SecurityPlugin SocketPlugin Now add some external plugins by dragging the following entries to the "External plugins" panel: UUIDPlugin UnixAioPlugin UnixOSProcessPlugin XDisplayControlPlugin Click the "Clean out" button to make sure the output directory is empty. This is not really necessary now, but it is good practice, and you will want to do it any time you want to guarantee that you are generating a complete fresh copy of the VM sources. In the "Generate:" panel, click the "Entire" button. This will generate all of the VM and plugin source code. In other words, it will translate the Smalltalk classes in your image into C code, and store the resulting source code in the "src" directory in your Squeak directory. This generated source, in combination with the platforms source code that you downloaded from the Subversion repository, is the complete source code for your new Squeak VM. Now go back to your Linux terminal window to compile and install the VM. You will need to have the CMake package installed on your Linux system, so make sure this is done before proceeding. You should now have all necessary sources in the "platforms" and "src" directories in your Squeak working directory: lewis@linux-jh8m:~/squeak/Squeak4.3> ls -ltd platforms src drwxr-xr-x 4 lewis users 4096 2011-11-19 10:10 src lrwxrwxrwx 1 lewis users 15 2011-11-19 09:39 platforms -> trunk/platforms Create a "build" directory for building the VM, and change into that directory: lewis@linux-jh8m:~/squeak/Squeak4.3> mkdir build lewis@linux-jh8m:~/squeak/Squeak4.3> cd build lewis@linux-jh8m:~/squeak/Squeak4.3/build> We will first run a configuration procedure that uses CMake to configure the sources for your system. You will find documention for this in platforms/unix/CMake.txt. The script that runs this procedure has introductory help, so read this first: lewis@linux-jh8m:~/squeak/Squeak4.3/build> ../platforms/unix/cmake/configure --help Now, from your empty build directory, run the actual configuration process. The parameters specify the location of the generated sources, and also specify that GL libaries should be avoided (they are not needed for this simple build, and might cause problems if you do not have the necessary libraries in place). If you are using a 64-bit operating system, this configuration will build a 64-bit VM (see the configuration help above if you want to specify CFLAGS to build a 32-bit VM, which you may later want to do if you are building some of the plugins that work in 32-bit mode). lewis@linux-jh8m:~/squeak/Squeak4.3/build> ../platforms/unix/cmake/configure --src=../src --without-gl When the configuration is complete, use make to build the VM: lewis@linux-jh8m:~/squeak/Squeak4.3/build> make If you have any errors or problems with the build, you may need to do some troubleshooting. In most cases the problem will relate to missing development software that you will need to install on your Linux system. When the build is complete, your new VM is read to be installed. lewis@linux-jh8m:~/squeak/Squeak4.3/build> make install Depending on the security settings of your system, you may need to log in as root (or use sudo) to perform this last step (but never use root access for any of the other build steps described above). Your new Squeak VM is now built and installed, ready to be run as /usr/local/bin/squeak. You can verify the version of the VM you are running as follows: lewis@linux-jh8m:~/squeak/Squeak4.3/build> squeak -version 4.7.14-2515 #1 XShm Sat Nov 19 10:27:11 EST 2011 gcc 4.5.0 Linux linux-jh8m 2.6.34.7-0.7-desktop #1 SMP PREEMPT 2010-12-13 11:13:53 +0100 x86_64 x86_64 x86_64 GNU/Linux plugin path: /usr/local/lib/squeak/4.7.14-2515 [default: /usr/local/lib/squeak/4.7.14-2515/] Congratulations, you are now a VM builder. You will probably want to add some more plugins, and you can save and load your VMMaker configurations for various combinations of plugins with the "Load" and "Save" buttons on your VMMaker window. For reference, here is a configuration file that matches the configuration of recent official Unix Squeak VMs on www.squeakvm.org (note that you will need to locate and install KedamaPlugin and GStreamer plugin to build a VM that fully matches the standard Unix VM). Contents of standard-vmmaker-unix.config file: #(#(#ADPCMCodecPlugin #AsynchFilePlugin #BMPReadWriterPlugin #BalloonEnginePlugin #BitBltSimulation #CroquetPlugin #DSAPlugin #DeflatePlugin #DropPlugin #FFTPlugin #FT2Plugin #FilePlugin #FloatArrayPlugin #FloatMathPlugin #GeniePlugin #JPEGReadWriter2Plugin #JPEGReaderPlugin #JoystickTabletPlugin #KlattSynthesizerPlugin #LargeIntegersPlugin #LocalePlugin #MD5Plugin #Matrix2x3Plugin #MiscPrimitivePlugin #RandPlugin #RePlugin #SHA256Plugin #SecurityPlugin #SerialPlugin #SlangTestPlugin #SlangTestSupportPlugin #SocketPlugin #SoundCodecPlugin #SoundGenerationPlugin #SoundPlugin #StarSqueakPlugin #SurfacePlugin ) #(#B3DAcceleratorPlugin #B3DEnginePlugin #ClipboardExtendedPlugin #DBusPlugin #FFIPlugin #FileCopyPlugin #GStreamerPlugin #HostWindowPlugin #KedamaPlugin #KedamaPlugin2 #MIDIPlugin #Mpeg3Plugin #RomePlugin #UUIDPlugin #UnixAioPlugin #UnixOSProcessPlugin #XDisplayControlPlugin ) true false 'unix' 'src' 'platforms' 4 true true 'Interpreter' )

1 0

KeyboardEvent differences between platforms
by Guillermo Polito 06 Nov '11

06 Nov '11

In TextEditor>>initializeShiftCmdKeyShortcuts the shortcuts are set in a way that it creates three handlers for each shortcut to make it work xD. The main difference here is that in Linux, ubuntu 11.04 the Ctrl+a comes with the right keyCharacter, but in Windows and MacOS it does not :(. We've tested that on host OSs with friends :). I've captured the problem I'm experimenting so far and wrote down an ugly hack in this method. KeyboardEvent>>modifiedCharacter self flag: #hack. "Hack me. When Ctrl is pressed, the key ascii value is not right and we have to do this shit" ^(self controlKeyPressed and: [ (#(MacOSX Windows) includes: Smalltalk os current platformFamily) and: [ keyValue <= 26 ]]) ifTrue: [ (self keyValue + $a asciiValue - 1) asCharacter ] ifFalse: [ self keyCharacter ] But I'd like to replace that by: KeyboardEvent>>modifiedCharacter ^self keyCharacter :P Are there any technical reasons why the Sensor behaves like that? How difficult is it to make it work the same for all three vms? Thanks! Guille

1 0

Better keyboard support
by Guillermo Polito 06 Nov '11

06 Nov '11

Hi! I'd like to introduce the function keys into the ones the sensor senses :). Actually, as I've tested in linux (ubuntu 11.04), the sensor only captures F11 and F12, but I'd like the other function keys to have nice Debugger shortcuts ;). Can someone point me where to look at the vm code? And maybe some tips will be useful since I'm a vm ignorant, jeje :P Thanks! Guille

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

VM-beginners November 2011