[LLVMbugs] [Bug 196] [vmcore] OpaqueType objects memory leak
bugzilla-daemon at zion.cs.uiuc.edu
bugzilla-daemon at zion.cs.uiuc.edu
Tue Dec 23 15:49:04 PST 2003
http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=196
sabre at nondot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Keywords| |quality-of-implementation
Resolution| |FIXED
Summary|OpaqueType objects memory |[vmcore] OpaqueType objects
|leak |memory leak
Target Milestone|--- |1.2
------- Additional Comments From sabre at nondot.org 2003-12-23 17:49 -------
The main patch is here:
http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20031222/010442.html
The problem was that the PATypeHolder object was addref'ing types when it was
created, but not dropRef'ing the type when it was destroyed. Whoops.
Fixing this exposed the following latent bugs in the asmparser:
http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20031222/010439.html
http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20031222/010440.html
-Chris
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the llvm-bugs
mailing list