https://bugs.kde.org/show_bug.cgi?id=405782
--- Comment #11 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to wavexx from comment #10) > Do you still think the buffer sizes should be hard-coded though? > > I know you can recompile and all, and theoretically this should never > happen, but I do expect debugging tools to never fail on crappy input ;) There are advantages and disadvantages to the current approach: As I understand, in terms of software layers, the VEX lib does not have any dependencies to the valgrind memory management layer/address space manager. Have memory sized at startup would break this. Also, when these max are exceeded, this is really an (efficiency) bug. Maybe it might also slightly impact the performance. But for sure, it not nice to have valgrind crashing on valid programs. -- You are receiving this mail because: You are watching all bug changes.
