]> git.ipfire.org Git - thirdparty/valgrind.git/commit
follow up to fix for 339721 assertion 'check_sibling == sibling' failed in readdwarf3...
authorPhilippe Waroquiers <philippe.waroquiers@skynet.be>
Tue, 7 Oct 2014 20:35:06 +0000 (20:35 +0000)
committerPhilippe Waroquiers <philippe.waroquiers@skynet.be>
Tue, 7 Oct 2014 20:35:06 +0000 (20:35 +0000)
commit2e547da1cadce72d7238efcb2b653a18cb4f1c4f
treeac3a4bb60583b21eaef5025c38af2ce88d7ba26e
parent97dc43567713d30b9c0754828cb74f77b4857ee0
follow up to fix for 339721 assertion 'check_sibling == sibling' failed in readdwarf3.c ...

The fix committed in revision 14603 is properly fixing the bug 339721.
However, when enabling the dwarf tracing, the DW_FORM_ref_sig8 causes
a segmentation violation, as the tracing code is shared with the
reading code. But the DW_FORM_ref_sig8 reading code is dereferencing
some data structure that is only initialised when --read-var-info=yes.

So, in case DW_FORM_ref_sig8 form reading is done and --read-var-info=no,
then check that we are tracing, and avoid dereferencing the (not initialised)
signature hash table.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14610
NEWS
coregrind/m_debuginfo/readdwarf3.c