|
From: <sv...@va...> - 2006-08-28 23:00:02
|
Author: sewardj
Date: 2006-08-28 23:59:58 +0100 (Mon, 28 Aug 2006)
New Revision: 6041
Log:
Merge r6040 (fix for: 'cfsi->len > 0 && cfsi->len < 2000000' failed)
Modified:
branches/VALGRIND_3_2_BRANCH/coregrind/m_debuginfo/storage.c
Modified: branches/VALGRIND_3_2_BRANCH/coregrind/m_debuginfo/storage.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- branches/VALGRIND_3_2_BRANCH/coregrind/m_debuginfo/storage.c 2006-08-=
28 22:56:59 UTC (rev 6040)
+++ branches/VALGRIND_3_2_BRANCH/coregrind/m_debuginfo/storage.c 2006-08-=
28 22:59:58 UTC (rev 6041)
@@ -308,7 +308,13 @@
ML_(ppDiCfSI)(cfsi);
}
=20
- vg_assert(cfsi->len > 0 && cfsi->len < 2000000);
+ /* sanity */
+ vg_assert(cfsi->len > 0);
+ /* If this fails, the implication is you have a single procedure
+ with more than 5 million bytes of code. Which is pretty
+ unlikely. Either that, or the debuginfo reader is somehow
+ broken. */
+ vg_assert(cfsi->len < 5000000);
=20
/* Rule out ones which are completely outside the segment. These
probably indicate some kind of bug, but for the meantime ignore
|