[LLVMdev] Troubleshooting Internal Garbage Collection

Duncan Sands baldrick at free.fr
Mon Jan 14 01:14:39 PST 2013

Hi David,

 > Previously, I had been testing with only one routine per test .ll file, but I
> thought I'd reached a point where I could test multiple operations at once and
> understand the output. The odd part about this is that the likelihood of seeing
> the above assertion scales with the number of functions in the .ll file. If I
> have one or two functions, I never see it. With three, I see it sporadically.
> With four or five, I see it about 80% of the time. I don't understand why it
> would only assert some of the time, as the inputs are not changing.

memory corruption or uninitialized variable maybe?  Try running under valgrind.

Ciao, Duncan.

  Could it be
> a problem with my system itself, or perhaps I'm running low on RAM? If anybody
> has any insight on how to troubleshoot this kind of problem, i'd be very grateful.
> Also, I have not overriden runOnMachineFunction() in my XXXISelDagToDag.cpp
> file, so this is happening somewhat out of my control. Should I attempt to
> override it? I noticed that only a couple targets actually override
> runOnMachineFunction() for that particular pass (MIPS, I think is one).
> Sincerely,
> ~MathOnNapkins / Dave
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

More information about the llvm-dev mailing list