> From a quick look at the source the assert is not related to some array
> limit or such. So you might just get lucky with what I described.
If this assertion is not tied to any possible damage it may cause, can it be
removed or perhaps turned into a warning?
BTW. After removing the assertion, the process runs much further, but
eventually (after a day) valgrind hangs somewhere and stops consuming the CPU.
First time ever I have seen such behaviour, at the same time our processes have
always stretched valgrind.
Greg
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
