This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/16426] memory corruption (use after free) with fission
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 10 Jan 2014 05:45:04 +0000
- Subject: [Bug symtab/16426] memory corruption (use after free) with fission
- Auto-submitted: auto-generated
- References: <bug-16426-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16426
--- Comment #3 from dje at google dot com ---
make check RUNTESTFLAGS='--target_board=fission mi-var-cmd.exp'
There are several failures, these are representative, the memory containing the
symbols names for v1,v2 has been reused:
FAIL: gdb.mi/mi-var-cmd.exp: create varobj for v1
FAIL: gdb.mi/mi-var-cmd.exp: create varobj for v2
I don't always see the failures, it presumably depends on how memory gets
reused.
Presumably something is always visible with valgrind.
cd testsuite
valgrind ../gdb =i=mi <16426.transcript
The attached valgrind output is what I see.
--
You are receiving this mail because:
You are on the CC list for the bug.