The following memory leak is detected by valgrind:
==23500== by 0x807AE94: x86_operand_new (in
/repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
==23500== by 0x807D9A5: ia32_decode_operand (in
/repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
==23500== by 0x807BA3D: ia32_decode_insn (in
/repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
==23500== by 0x807C0D9: ia32_disasm_addr (in
/repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
==23500== by 0x807A2D8: x86_disasm (in
/repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
==23500== by 0x8079AF9: google_breakpad::DisassemblerX86::NextInstruction()
(in /repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
==23500== by 0x8053099: (anonymous
namespace)::DisassemblerX86Test_BadReadXCHGThenWrite_Test::TestBody() (in
/repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
==23500== by 0x805B30D: testing::Test::Run() (in
/repos/google-breakpad/tot/out/src/processor/disassembler_x86_unittest)
Original issue reported on code.google.com by benc...@chromium.org on 30 Mar 2012 at 8:57
Original issue reported on code.google.com by
benc...@chromium.org
on 30 Mar 2012 at 8:57