On Sunday 03 August 2003 15:27, Simon Glover wrote: > On 3 Aug 2003, Luke Palmer wrote: > > This fix has worked fine with JIT until now, so I suspect the problem > > is elsewhere. > > Bug confirmed here (although I need a slightly longer string to trigger > it). Here's a stacktrace:
I couldn't reproduce it here, but from your bt I supposed that jit_info->objfile was getting something (!= NULL) while running under jit, as it was not initialized correctly, so I fixed that. Could you confirm if the bug's still there? > > Simon Daniel
