Hi all,
As you may know, Valgrind checks if there are no procedures bigger than
5bln bytes in debugged/profiled binary. It uses assert placed in
*coregrind/m_debuginfo/storage.c:723* line (at least in version 3.11.0).
That big procedures are unexpected and should not appear. Well... I have a
piece of code where it occur (5004720 bytes procedure) :)
I have commented out this line and recompiled Valgrind. It works fine now,
but
does anyone know if it's possible to prevent Valgrind asserting this by - I
don't know - maybe a command line flag/option? To bypass that
comment-recompile step.
Thanks,
Wojtek
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
