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
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:
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.r
Yes, your understanding is absolutely correct. I should say I'm pleased
to receive such a good questions, because it proves that I express my
ideas and describe Avalanche quite clearly.)
Avalanche is more likely to find a bug if it is close to the program
entry point. Finding deep errors is als
d-users@lists.sourceforge.net
> Subject: Re: [Valgrind-users] Valgrind tool for generating 'inputs of
> death'
>
> 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 disco
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
On Wednesday 26 May 2010, Dallman, John wrote:
> 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 synth
From: Ildar Isaev [mailto:iis...@ispras.ru]
> Sent: Wednesday, May 26, 2010 2:13 PM
> To: valgrind-users@lists.sourceforge.net
> Subject: Re: [Valgrind-users] Valgrind tool for generating 'inputs of
> death'
>
> Well, there is no such a definite limit - I just used files of t
Avalanche analyzes an entire application at once. I suppose the same
approach may be applied to analyzing separate functions, but currently
it just analyzes the whole application.
So what is "input of death"? At first i focused on analyzing
applications that get their input data from some inpu
om
> Tel: +44-1223-371554
> john.dall...@siemens.com
> www.siemens.com/plm
>
> From: Ildar Isaev [mailto:iis...@ispras.ru]
> Sent: Wednesday, May 26, 2010 1:43 PM
> To: valgrind-users@lists.sourceforge.net
> Subject: Re: [Valgrind-users] Valgrind tool for generating 'inputs of dea
ridge, CB2 1DP
United Kingdom
Tel: +44-1223-371554
john.dall...@siemens.com
www.siemens.com/plm
From: Ildar Isaev [mailto:iis...@ispras.ru]
Sent: Wednesday, May 26, 2010 1:43 PM
To: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Valgrind tool for generating 'inputs of death
So here is the preprint.
http://docs.google.com/uc?export=download&id=0B8tMFqXJ6Zw0MjJlNmJmMTYtMjNiYS00OGUyLTg3ODMtMjQ3NmQyMDRiMjU3
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 c
Julian Seward wrote:
> 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).
Same here. I have a fairly basic question: in what terms does
Av
On Tue, May 25, 2010 at 5:45 PM, Ildar Isaev wrote:
> 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
On Tue, May 25, 2010 at 4:19 PM, Julian Seward wrote:
>
>> > The easiest thing to do for a start is put a full fork of valgrind +
>> > Avalanche up on a repository somewhere. That way at least people can
>> > see and use it while you decide if you want to take the support hit of
>> > keeping up wi
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 Compu
> > The easiest thing to do for a start is put a full fork of valgrind +
> > Avalanche up on a repository somewhere. That way at least people can
> > see and use it while you decide if you want to take the support hit of
> > keeping up with the main Valgrind branch.
Did the message that the above
Yes, setting up a standalone repository is surely the most obvious way.
This is may be a good thing for a start, but I suppose it won't give
Avalanche that many users. So joining the main Valgrind branch is a
desired thing.) Is it really possible and what should be done for that?
Should I proba
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
19 matches
Mail list logo
