Hi Nicolas,

can you easily determine if all the DLLs in a Win64 application are within the 4Gb 32-bit address space or occupy a 64-bit address space? The VMProfiler needs to sample pcs in the range occupied by code. On 64-bits it will benefit from using only a 32-bit address space. On Mac OS X all shared libraries in the VM are within the 32-bit address space, so the existing code works. Alas on Linux x86 the shared libraries start at about the half-way point through the 64-bit address space (16r7f ff ff ff ff ff ff ff), so one has to use a full 64-bit buffer for pc samples. I don't know what happens with win64 and have yet to create my win64 parallels VM. perhaps you could check for me. Thanks.

On Thu, Sep 29, 2016 at 4:20 PM, GitHub noreply@github.com wrote:

Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: 3b4b6b30caea8fb139d2fb8b820c9033c2b88db5 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/ 3b4b6b30caea8fb139d2fb8b820c9033c2b88db5 Author: Eliot Miranda eliot.miranda@gmail.com Date: 2016-09-29 (Thu, 29 Sep 2016)

Changed paths: M build.linux32ARMv6/HowToBuild M platforms/unix/vm/sqUnixVMProfile.c

Log Message:

Allow 32-bit PC samples on 64-bit platforms in the VMProfiler, defaulting to 32-bit samples on Mac OS X. Update instructions for instaling Open GL on Raspbian (Debian).