1) 10 Kb is not that terribly big either - it still makes sense trying to run the analysis and examine the results
2) Avalanche is good in discovering errors on 'sad paths' - i. e. when the program is run on some kind of malformed input. And one can usually stick quite enough malformation even into short files:) 3) Don't be very strict to Avalanche - it is just a research, which results greatly exceeded my expectations. So now I'm just thinking about better ways of sharing my work and getting some feedback. Of course, there's still a room for improvement. > This is fine with some kinds of data. One can make a smaller bitmap, > or a shorter sound clip. But with what I do - accurate 3D shape > representation - one can't get anything meaningful into 1KB or so. > I just took a look at our directory of synthetic test parts, and > there are some under 1KB, but they are mostly null cases. You > start to get non-trivial data at 10KB or so sizes. This doesn't > make Avalanche useless, but it does limit it fairly seriously. > > best, > > -- > John Dallman > Parasolid Porting Engineer > ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
