similar to: [LLVMdev] Advice on debugging?

Ping? Still looking for advice in figuring out how and why my generated code is causing lli to crash... Talin wrote: > I've been using lli to do most of my unit tests for the compiler that > I'm writing. However, when I get a test that crashes, its difficult to > find which instruction it was that caused the crash. I tried running > bugpoint, but it didn't seem to work

> I am having the same problem. It was "introduced" by revision 54811, > so it looks like a memory corruption problem. Investigating. Interesting. Bootstrapping with gcac works! Some tests with valgrind also work. My next try is to add some debug code to do bounds checking in SmallVector. Cheers, -- Rafael Avila de Espindola Google | Gordon House | Barrow Street | Dublin 4 |

I get the error below (and have for a couple weeks now) when trying to build llvm-gcc on Ubuntu Feisty. In the meantime, on Ubuntu Gutsy, everything has been building fine. Both are release builds for x86. John cc1: StringMap.cpp:177: void llvm::StringMapImpl::RemoveKey(llvm::StringMapEntryBase*): Assertion `V == V2 && "Didn't find key?"' failed.

I'm getting the following when building llvm-gcc with an optimized set of LLVM libraries: /ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/xgcc -B/ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/ -B/cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/

> Ping? Still looking for advice in figuring out how and why my generated > code is causing lli to crash... Did you run your code through the verifier? > > So for example, when I run lli on my program: > > ---------------------------------------------------------- > > Assertion failed: (V == V2 && "Didn't find key?"), function RemoveKey, > >

David Greene wrote: > I'm getting the following when building llvm-gcc with an optimized set of > LLVM libraries: > > /ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/xgcc > -B/ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/ >

This series of patches address several issues causing memory usage to grow indefinetely on a long lived process. These are not convenional leaks -- memory would have been freed when the LLVM context or/and JIT engine is destroyed -- but for as long as they aren't the memory is usage effectively ubounded. The issues were found using valgrind with '--show-reachable=yes' option: 1.

On Mar 16, 2008, at 5:07 AM, Duncan Sands wrote: >> Did anything ever come of the work on exception handling for x86_64? >> >> I'm having problems with exceptions on linux x86_64. > > I'm fairly sure that exception handling doesn't currently work on > x86-64 linux (it may work with darwin - not sure). I don't know > what it would take to get it to

On Tue, Sep 2, 2008 at 12:08 PM, John Regehr <regehr at cs.utah.edu> wrote: > I get the error below (and have for a couple weeks now) when trying to > build llvm-gcc on Ubuntu Feisty. In the meantime, on Ubuntu Gutsy, > everything has been building fine. Both are release builds for x86. I've seen this error too with gcc version 4.1.2 20070626 (Red Hat 4.1.2-14). I do not see

http://bugzilla.mindrot.org/show_bug.cgi?id=436 Summary: SSH client API Product: Portable OpenSSH Version: 3.5p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: jensus at linux.nu I would

Hi, When i wanted to build the llvm-gcc, i got the problem as following. ========================================================================================================================== cc1: /home/cllou/LLVM/llvm-2.4-dir/llvm-2.4/lib/Support/StringMap.cpp:177: void llvm::StringMapImpl::RemoveKey(llvm::StringMapEntryBase*): Assertion `V == V2 && "Didn't find