> So if one wants to find a bug with Avalanche, one should be > better take shorter files. There's just more chance to detect > anything.
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 Siemens Product Lifecycle Management Software Industry Sector 46 Regent Street, Cambridge, CB2 1DP United Kingdom Tel: +44-1223-371554 [email protected] www.siemens.com/plm > -----Original Message----- > From: Ildar Isaev [mailto:[email protected]] > Sent: Wednesday, May 26, 2010 2:13 PM > To: [email protected] > Subject: Re: [Valgrind-users] Valgrind tool for generating 'inputs of > death' > > Well, there is no such a definite limit - I just used files of this > length for testing. > > But, obviously, the greater the size of the input file, the more chance > there is that the analysis will take quite a long time. Because if the > file is big, the constraints that need to be checked will contain many > variables, and SAT-solving is not very fast. > > So if one wants to find a bug with Avalanche, one should be better take > shorter files. There's just more chance to detect anything. > > > I'm not clear where the restriction of files to 712 bytes comes from; > > is that an arbitrary limit to ensure that analysis takes a sane length > > of time? > > > > thanks, > > > > -- > > John Dallman > > Parasolid Porting Engineer > > > > Siemens Product Lifecycle Management Software > > Industry Sector > > 46 Regent Street, Cambridge, CB2 1DP > > United Kingdom > > Tel: +44-1223-371554 > > [email protected] > > www.siemens.com/plm > > > > From: Ildar Isaev [mailto:[email protected]] > > Sent: Wednesday, May 26, 2010 1:43 PM > > To: [email protected] > > Subject: Re: [Valgrind-users] Valgrind tool for generating 'inputs of > death' > > > > So here is the preprint. > > > > > http://docs.google.com/uc?export=download&id=0B8tMFqXJ6Zw0MjJlNmJmMTYtMj > NiYS00OGUyLTg3ODMtMjQ3NmQyMDRiMjU3 > > > > Page 4 is may be a bit malformed (I haven't received the corrected > version from the publishing yet), so please feel free to ask any > questions if anything is not clear. > > > > > > > > It sounds interesting. I would like to read more about it and > > perhaps try it out, to get some idea of its effectiveness on > > large programs (ability to find bugs, false error rate, speed > > and memory use). > > > > > > provide a preprint for the article that is going to be > > published in "Programming and Computer Software" journal > > (http://www.maik.rssi.ru/cgi-perl/journal.pl?lang=eng&name=procom) > soon. > > > > > > I would be interested to read that. > > > > J > > > > > > > > > ------------------------------------------------------------------------ > ------ > > _______________________________________________ > Valgrind-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/valgrind-users ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
