search for: getkeylength

Hi, > Today I've been trying to debug a weird bug that makes JIT crash with > certain code and when using the inliner. This may sound weird, but if I > disable the inliner, it doesn't crash. > I include an example gdb dump below. Does something looks wrong? Do you > think it's a bug in JIT or it's just some other piece of code that is > writing on the JIT

...inliner. Running valgrind on the program without the inliner doesn't show any error. If I run the program with the inliner (just uncoment 1 line), valgrind gives a few errors. Example of one of the errors: ==11384== Invalid read of size 4 ==11384== at 0x54B6F04: llvm::StringMapEntryBase::getKeyLength() const (StringMap.h:47) ==11384== by 0x59C6CFD: llvm::Value::getNameStr() const (Value.cpp:162) ==11384== by 0x544FE54: llvm::Value::getName() const (Value.h:110) ==11384== by 0x55E7DA8: (anonymous namespace)::JITResolver::JITCompilerFn(void*) (JITEmitter.cpp:269) ==11384== by 0x54AA...

Hi, Today I've been trying to debug a weird bug that makes JIT crash with certain code and when using the inliner. This may sound weird, but if I disable the inliner, it doesn't crash. I include an example gdb dump below. Does something looks wrong? Do you think it's a bug in JIT or it's just some other piece of code that is writing on the JIT memory?.. I don't really know