Strange Jedi crashes on Mac OS X

[Guillaume Cartier]

Some people have reported a very strange bug on Mac OS X.

After a full build of jedi :

running bin/jedi would crash but

running bin/kernel -run jedi would run ok

After some bug hunting, it seems it boils down to a bug in Gambit's new module-name: option to compile-file-to-c. A temporary patch was pushed to the repo until Marc can confirm / solve that this is indeed a bug in Gambit.

To fix a crashing Jedi, simply pull the latest changes from the repo, cd to the directory containing the jedi executable and do :

kernel -compile jedi -force

Guillaume

[Guillaume Cartier]

In the previous message I forgot to mention that "kernel -compile jedi
-force" relies on a new -force option of the Jazz kernel.

So before running that command you will need to rebuild your kernel
with "gsc make kernel" or "gsc make jedi".

Guillaume

On Nov 17, 11:45 am, Guillaume Cartier <gcart...@jazzscheme.org>
wrote:

[Guillaume Cartier]

Update on this bug.

After discussing this with Marc, the bug was due to a fundamental assumption in Gambit that every module name should be unique. When linking an executable like jedi, the flat link file generated must be named jedi.c hence the clash with the jedi module.

So, the patch we did to add a uniqueness prefix to compiled module names seems not to be a patch after all but the right solution :)

Guillaume 

--

You received this message because you are subscribed to the Google Groups "Jazz Scheme" group.
To post to this group, send email to jazzs...@googlegroups.com.
To unsubscribe from this group, send email to jazzscheme+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jazzscheme?hl=.