I suppose you probably have an old version of automake/autoconf. The
version should be >= 1.10. There's something wrong with Valgrind
configuration in older versions.
Hello,
I tried to install the application, but I could not do it. I got the
following errors.
Regards,
Juan Carlos
**********************
In file included from m_cpuid.S:31:
pub_core_basics_asm.h:42:33: error: pub_tool_basics_asm.h: No such
file or directory
pub_core_basics_asm.h:45:20: error: config.h: No such file or directory
make[4]: *** [libcoregrind_x86_linux_a-m_cpuid.o] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [tracegrind] Error 2
On Wed, Jun 23, 2010 at 11:35 AM, Ildar Isaev <[email protected]> wrote:
OK, so i released Avalanche on Google Code:
http://code.google.com/p/avalanche/
I hope it will be useful (at least for somebody). Any feedback is welcome.
Best regards,
Ildar
Hello,
I'm Ildar Isaev, a researcher and software developer at Institute for System
Programming (http://www.ispras.ru/en/), Russia, Moscow.
In the last fifteen months I was working on a research project, which main
goal was to investigate the possibility of using dynamic analysis in order
to generate 'inputs of death' - such a values of input data that cause some
critical bug in the analyzed program to happen. As a result of this
research, I developed a tool (it is named Avalanche), that successfully
found a number of bugs in the open source projects (see the attachment for
their list) and generated input data that reproduces these bugs. Most of
these bugs are confirmed and fixed by the developers.
Speaking in very brief, Avalanche consists of a Valgrind plugin (it is also
developed by me), which tracks the flow of tainted data in the analyzed
program and emits special constraints, and a third party constraint solver
that checks the satisfiability of the emitted constraints. Some of the
constraints are emitted to achieve automatic path alternation, the rest are
emitted to check for the possible bugs in the certain situations.
The number of bugs discovered by Avalanche lets me hope that Avalanche can
become really valuable as a defect detection tool. So now I'm thinking about
releasing it "into the wild".
Are you interested in such a tool? If so, I may give a more detailed
description or 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. Can
Avalanche probably become one of the Valgrind tools one day?
Best regards,
Ildar
________________________________
------------------------------------------------------------------------------
________________________________
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
