[Vm-dev] RE: Linux vm

Schwab,Wilhelm K bschwab at anest.ufl.edu
Mon Aug 23 13:19:43 UTC 2010


It can still be a serious problem as performance can suffer.  In fact, in this case, I am talking about Shared Libraries, not plugins.  There is no fallback code; one succeeds in loading the library or the game is over.

strace might do the job, but what is wrong with having the vm log what it is trying to do?


From: K. K. Subramaniam [kksubbu.ml at gmail.com]
Sent: Monday, August 23, 2010 2:33 AM
To: vm-dev at lists.squeakfoundation.org
Cc: Schwab,Wilhelm K; Pharo-project at lists.gforge.inria.fr
Subject: Re: [Vm-dev] RE: Linux vm

On Sunday 22 Aug 2010 8:09:22 am Schwab,Wilhelm K wrote:
> Is there a way to get such diagnostic information without hacking the vm
> source?  If not, please consider the following as a proposed patch.  I
> have tried to strike a balance between seeing enough to make sense of
> errant plugin paths and giving detailed information about failures when
> given an absolute path
In your place, I would have tried ldd(1) or strace(1) to detect path load

In general, failing to load a plugin module is not a fatal error. Sometimes, a
primtive can fallback to using internal routines if the plugin is not


More information about the Vm-dev mailing list