[Pharo-project] struggeling along
Hi, I can't really follow the mailing list so some of these might already known and fixed. I just tried to install a gemtools client from universe. I'm using the latest pharo-dev. Installing FFI brought up an syntax error because there is an attempt writing to a temp. Did this change with the closures? I think this is fixed by the version some can load via the ScriptLoader. Next I encountered a problem with MIMEDocument. I think it is Issue-631. There is an incorrect usage of the MIMEDocument interface. I changed it but wanted to store it in PharoInbox but my image crashes if I try to. It is: Segmentation fault -1178673304 UUID>initialize -1178673420 Behavior>new: -1178673512 >new I updated my vm to exupery-0.15.1 but still has the same behaviour. I attached a patch for the MIMEDocument issue on Issue-631. Than I met InputSensor. InputSensor default returns an instance of InputEventSensor. This looks just strange to me. Is this right? Norbert
On Thu, 2009-05-28 at 23:09 +0200, Michael Rueger wrote:
On Thu, May 28, 2009 at 11:06 PM, Norbert Hartl <norbert@hartl.name> wrote:
Than I met InputSensor. InputSensor default returns an instance of InputEventSensor. This looks just strange to me. Is this right?
Welcome to the input event/sensor refactoring ;-)
I take this as a "yes"! :) Norbert
On May 28, 2009, at 23:06 , Norbert Hartl wrote:
Hi,
I can't really follow the mailing list so some of these might already known and fixed. I just tried to install a gemtools client from universe. I'm using the latest pharo-dev.
Installing FFI brought up an syntax error because there is an attempt writing to a temp. Did this change with the closures? I think this is fixed by the version some can load via the ScriptLoader.
Next I encountered a problem with MIMEDocument. I think it is Issue-631. There is an incorrect usage of the MIMEDocument interface. I changed it but wanted to store it in PharoInbox but my image crashes if I try to.
It is:
Segmentation fault
-1178673304 UUID>initialize -1178673420 Behavior>new: -1178673512 >new
Thanks for the feedback. The segfault probably is #855 (I just created this issue now. The problem has been discussed on May 19). Cheers, Adrian
participants (3)
-
Adrian Lienhard -
Michael Rueger -
Norbert Hartl