What environment is this? Some JITs work better than others. On Aug 10, 2010, at 1:35 PMPDT, Eric Christopher wrote:> On Aug 10, 2010, at 1:30 PM, Bueno, Denis wrote: > >> Running lli under gdb gives >> >> Program received signal SIGSEGV, Segmentation fault. >> [address] in ?? () >> (gdb) bt >> #0 [address] in ?? () >> Cannot access memory at address [address2] >> >> Wow. Something has really trashed your stack. > >> Was sqlite3 part of the llvm-2.6 test suite? If so, it is likely >> there’s a workaround for 2.6. > > It may have been, that's been a while. It is now for sure and was > at the 2.7 time frame. We don't keep release branches around so ...sqlite3 was added to the testsuite in March 2008. When was 2.6?
On Aug 10, 2010, at 1:39 PMPDT, Dale Johannesen wrote:>> >>> Was sqlite3 part of the llvm-2.6 test suite? If so, it is likely >>> there’s a workaround for 2.6. >> >> It may have been, that's been a while. It is now for sure and was >> at the 2.7 time frame. We don't keep release branches around so ... > > sqlite3 was added to the testsuite in March 2008. When was 2.6?Released Oct 2009, so sqlite3 was in the testsuite at that time for sure. It was tested in many environments before release.
On 8/10/10 2:39 PM, "Dale Johannesen" <dalej at apple.com> wrote:> What environment is this? Some JITs work better than others.Ubuntu Lucid, x86_64. -Denis
On Aug 10, 2010, at 1:47 PMPDT, Bueno, Denis wrote:> On 8/10/10 2:39 PM, "Dale Johannesen" <dalej at apple.com> wrote: > >> What environment is this? Some JITs work better than others. > > Ubuntu Lucid, x86_64.No idea then. It was surely tested on x86-64 Linux, if not that exact variant.