<div><br></div><div><br><div class="gmail_quote">On Wed, Dec 28, 2011 at 13:18, Matthew Flatt <span dir="ltr"><<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for all the new info! I don't think that it's a bytcode problem.<br>
I start to wonder if it's in number parsing...<br>
<br>
On line 1102 of "src/racket/src/numstr.c", there's a call to STRTOD().<br>
Does it change anything if you wrap that call with calls to<br>
scheme_push_c_numeric_locale() and scheme_pop_c_numeric_locale(loc)?:<br>
<br>
{<br>
GC_CAN_IGNORE char *loc;<br>
loc = scheme_push_c_numeric_locale();<br>
d = STRTOD(ffl_buf, &ptr);<br>
scheme_pop_c_numeric_locale(loc);<br>
}<br></blockquote><div><br></div><div>It works!</div><div>Though: I downloaded the nightly Unix sources, and did:</div><div>mkdir build</div><div>cd build</div><div>../configure</div><div>make</div><div><br></div><div>
But no drracket executable appears (did I do something wrong?).</div><div>So I did:</div><div>gracket/gracket3m</div><div><br></div><div>and it took a full minute with 100% CPU to start (same for simply racket3m).</div><div>
Then </div><div><div>Welcome to Racket v5.2.0.7.</div><div>This is a simple window for evaluating Racket expressions.</div><div>Quit now and run DrRacket to get a better window.</div><div>The current input port always returns eof.</div>
<div>> .3</div><div>0.3</div><div>> </div></div><div><br></div><div><br></div><div>In case this does not completely solve the issue, here is another minimalistic interesting interaction in the buggy gracket:</div><div>
<div><br></div><div>Welcome to Racket v5.2.0.6.</div><div>This is a simple window for evaluating Racket expressions.</div><div>Quit now and run DrRacket to get a better window.</div><div>The current input port always returns eof.</div>
<div><div>> .3</div><div>0.0</div><div>> 3.3</div><div>3.0</div><div>> .3</div><div>0.3</div></div></div><div><br></div><div>So it seems that it's the fact that using a >= 1 floating point number make the bug go away.</div>
<div><br></div><div><br></div><div>Anyway, I hope this does solves the issue!</div><div>Thank you very much,</div><div><br></div><div>Laurent</div><div><br></div><div> </div></div><br></div>