[Vm-dev] RE: [Pharo-project] Debug-it and external calls

[Schwab,Wilhelm K]

So the external call does not happen and the fall-back code executes.  That explains it.  It might be nice if FFI calls could be made to happen, or at least to have a more informative error message, such as "Primitive not executed by the debugger" rather than "Unable to find function address."

Bill




________________________________________
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves at elte.hu]
Sent: Monday, July 19, 2010 12:20 PM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] Debug-it and external calls

On Mon, 19 Jul 2010, Schwab,Wilhelm K wrote:

> I often (not always??) find that using the Debug-it command and debugging into an external call (FFI) leads to a false claim of "Unable to find function address."  Stepping over the call works; stepping into it make it look like it fails.
>
> I am curently using a 1.1 RC2 image and the 4.0.3 vm on Ubuntu.  I cannot easily move the offending code to Windows, nor do I particularly care to do so (feels good<g>), and FFI is fairly uncommon in Squeak/Pharo.
>
> Can anyone else tinker with this to see if it is real?

IIRC when you're using the debugger, primitives are not evaluated.


Levente

>
> Bill
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project