Vm-dev January 2008

vm-dev@lists.squeakfoundation.org

15 participants
14 discussions

VMMaker wrong C translation
by Mathieu Suen 10 Jan '08

10 Jan '08

Hi, I have a wierd tranlation from VMMaker: The Squeak code is: (messageSelector = self splObj: SelectorNextObject) not ifTrue: [ .... ] the C is: if (!(longAt((foo->specialObjectsOop + BaseHeaderSize) + (SelectorNextObject << ShiftForWord)))) { } So the foo->messageSelector have despaired. Any idea why? Thanks Mth

2 2

How to build VideoForLinuxPlugin on linux?
by Nicolai Hess 06 Jan '08

06 Jan '08

Hi, I want use VideoForSqueak and for this I have to build the VideoForLinuxPlugin. So I checkout squeak-vm from svn and tried to select the VideoForLinuxPlugin in VMMaker. I can select most of the plugins, but not VideoForLinux. There is a message: "No cross platform files found for VideoForLinuxPlugin". My plattform is Linux of course, and the selected platform is unix. So I looked in the source for VideoForLinuxPlugin and InterpreterPlugin. There are selectors "InterpreterPlugin>>requiresCrossPlatformFiles" ^self hasHeaderFile and "VideoForLinuxPlugin>>hasHeaderFile" ^true To solve this I added "VideoForLinuxPlugin>>requiresCrossPlatformFiles" ^false Now I can select this plugin and generate the sources. After configure, make stopps with an error like "XXX already defined ... first defined here ...." This is because makefile has now two entrys for "VideoForLinuxPlugin.lo" It tries to build one in the directory where I told VMMAker to put my platform-code (which is beneath my svn/platform "svn/src"): VideoForLinuxPlugin$o : <PATH_TO_SVN>/src/plugins/VideoForLinuxPlugin/VideoForLinuxPlugin.c $(COMPILE) VideoForLinuxPlugin$o <PATH_TO_SVN>/src/plugins/VideoForLinuxPlugin/VideoForLinuxPlugin.c And one in my svn-version : VideoForLinuxPlugin$o : <PATH_TO_SVN>/platforms/unix/plugins/VideoForLinuxPlugin/VideoForLinuxPlugin.c $(COMPILE) VideoForLinuxPlugin$o <PATH_TO_SVN>/platforms/unix/plugins/VideoForLinuxPlugin/VideoForLinuxPlugin.c commenting out on the second entry worked. FInally I get it to work, but I had to change VideoForLinuxPlugin source and the makefile. This was my first squeak-vm build, so maybe I did something wrong or is there a newer way to get input from a webcam in squeak? Nicolai _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

2 1

bug in the vm: bad retype from pointer to oop
by Marek Sterzik 02 Jan '08

02 Jan '08

Hello! I found a bug in the sources of the VM, which often causes segfaults. It happens when the VM is compiled for a 64bit architecture. On many places there is retyped from pointer to oop as: oop = (sqInt)(long)oop; but it should be: oop = oopForPointer(oop); This is at least for the unix architecture, and at least in some (more than one) plugins, specially in the SocketPlugin. On my system, the sqMemoryBase is not zero, so the two lines above makes two different pointers. Now, I have fixed the socket plugin, but if the source is generated, it would be a good idea to fix the generator. (And I have no idea how the generator works). Regards marek sterzik

2 1

Unix VM path encodings
by Andreas Raab 01 Jan '08

01 Jan '08

Hi - Due to a bug reported against Qwaq Forums I needed to look into how the Unix VM encodes file and path names and got terribly confused. My test case was to create a file with an Umlaut("Jürgen") and to see what both Squeak and the Unix shell reports with varying settings of -pathenc and -textenc. I started with the assumption that since the file system I was running this on is UTF-8 the default settings (-textenc MacRoman and -pathenc UTF-8) ought to be correct. However, the result was very surprising. The file name was reported incorrectly both in the file list as well as by the OS - the file list reported "J?" (truncated after the question mark) and the Unix shell reported "J?rgen" but with a "funky ?" (the glyph is hard to describe without a screenshot; it was neither an umlaut nor a regular question mark). Playing with the settings I could not find any combination that resulted in a consistent representation for all the different views - either the Unix shell was off or Squeak's view was off no matter how I set those encodings. Can someone explain to me how I need to set these values to get a consistent view on file names both from Squeak and Unix? Cheers, - Andreas

4 13

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev January 2008