Yes. This is really annoying for me. I am writing a C library plugin since a
year and a half and this is very frustrated :(
You cannot debug when using FFI. I mean, you cannot get advantages of one of
the best Smalltalk features! What I do is to write a self break before and
after the call and use "proceed" but I don't like it at all.

Once I tried to see what the problem was, but I was to difficult to me to
understand it and fix it. We need a guru here I think hahaha.

Best,

Mariano

2009/7/30 Javier Pimás <[email protected]>

> Hi, I'm having problems with the debugger. Every time I try to debug code
> that uses FFI, if I step over a message that internally does an FFI call, I
> get an externalCallFailed error and then I land in
> MethodContext(ContextPart)>>runUntilErrorOrReturnFrom:
> If I run the code without debugging, then I have no problems at all.
>
> I'm using SqueakPharo v3.11.2 with pharo0.1-10373web09.07.2.
>
> To reproduce it you can try this:
>
> ScriptLoader loadFFI.
> then load latest GLMorphic from squeaksource, and uncomment the "self
> break." in
> GLCanvas>>displayString:from:to:at:strikeFont:kern:
>
> doit
> World fullDrawOn: GLDisplayScreen testCanvas
> hit debug and step over until you reach
> ogl glTexImage2D: GLTexture2d with:...
>
> also you'll see wrong values for local vars, like aPoint which will look as
> #(nil nil nil nil nil) when it'll actually have a point.
>
> Is there any other way to set up a break point instead of adding self break
> to the code??
>
> Thanks,
>        Javier.
>
> --
> Javier Pimás
> Ciudad de Buenos Aires
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to