Dear Christophe,
Sorry for the late reply. Boriss Mejias and I have tried the code you
sent, and as you wrote in your former e-mail, we could not reproduce the
bug.
Can you send some code (even large) that reproduces the bug? I want to
investigate this, because the error is really weird (the code that is
run is incorrect, and should never be executed, in fact). You can send
it to me personally, if the code is confidential or very large.
Cheers,
raph
Christophe Taton wrote:
Hi all,
Any update, idea or suggestion on this? Any advice on what I
could/should do next? Tips for debugging? Give up?
Thanks
Christophe
On Fri, Apr 11, 2008 at 7:14 PM, Christophe Taton
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
Hi all,
The code fragment I posted in my previous mail is useless because it
seems specific to my laptop.
I have thus restarted from the original failing code that I reduced
to a "simple" failing code fragment.
Unfortunately, it appears to me that the bug is triggered when my
code fragment imports another (unused) module, with the condition
that this module contains a "significant amount of code"!
This means that when I try to remove some unused code from this
unused imported module, the bug disappears and the code fragment
executes correctly.
Is there any hope that someone could use this as a starting point
for a bug report??
I can ship the code if you are ready to look into this! Any help
will be very very much appreciated ;)
Thanks,
Christophe
------------------------------------------------------------------------
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
