2010/5/27 Jorge Moraleda :
> Dear all,
>
> Am I doing something wrong, or is is there a race condition somewhere
> in std::istringstream and/or std::getline?
>
> (Bart, Konstantin, this ended up being the error that I've been trying
> to track down for a while and that I thought --erroneously-- was
Dear all,
Am I doing something wrong, or is is there a race condition somewhere
in std::istringstream and/or std::getline?
(Bart, Konstantin, this ended up being the error that I've been trying
to track down for a while and that I thought --erroneously-- was
caused by std::locale)
This program:
Hi Mogens,
I removed --disable-tls from the configure command. The config.log shows that
the Altivec is supported.
./configure --host=powerpc-linux --target=powerpc-linux
--prefix=/myhome/download/valgrind
config.log:
..
configure:6942: checking for Altivec
configure:6973: ppc_4xx-g
Hi,
I don't know if this helps you, but what is the output from configure?
configure checks for altivec support, and it seems to me like this isn't
supported by your compiler.
I run valgrind on a ppc. The (cross)compiler (4.1.2) supports altivec, but
the CPU doesn't. And valgrind builds and ru
I meant, I commented out those Unrecognized opcode in the file,
m_dispatch/dispatch-ppc32-linux.S. But, I other error. Can someone please
help. Thanks.
--- On Wed, 5/26/10, Gary Yang wrote:
From: Gary Yang
Subject: Re: [Valgrind-developers] Valgrind cross compilation error for
PPC32_LIN
Hi,
I commented out those stvx, vand and vspltw etc. But, I got anther error. Can
someone help?
..
ppc_4xx-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub
-DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -m32 -O2 -g -Wall
-Wmissing-prototypes -Wshadow -Wpointer-arith -Wstric
Hi Bart,
Thanks for your reply. I read https://bugs.kde.org/show_bug.cgi?id=238745.
However, I did not find a solution. I added --disable-tls for configure. I
still got the error. Any idea?
./configure --host=powerpc-linux --target=powerpc-linux --disable-tls
--prefix=/projects/svdc/P4wsIPC
On Wed, May 26, 2010 at 9:05 PM, Gary Yang wrote:
> I used the command, svn co svn://svn.valgrind.org/valgrind/trunk valgrind
> got the trunk code. I would like to get the 3.5 branch code. Can someone
> tell me how?
>
Have you already tried the command below ?
svn ls svn://svn.valgrind.org/valg
Hi,
I used the command, svn co svn://svn.valgrind.org/valgrind/trunk valgrind got
the trunk code. I would like to get the 3.5 branch code. Can someone tell me
how?
Thanks,
Gary
--
___
On Wed, May 26, 2010 at 9:04 PM, Gary Yang wrote:
> [ ... ]
> m_dispatch/dispatch-ppc32-linux.S:142: Error: Unrecognized opcode: `stvx'
> [ ... ]
>
See also https://bugs.kde.org/show_bug.cgi?id=238745.
Bart.
--
___
Hi,
I cross compile Valgrind for PowerPC Linux, PPC32_LINUX. I got the code from
the trunk.
svn co svn://svn.valgrind.org/valgrind/trunk valgrind
I got the error when I do the cross compile. Can someone help?
Below are what I did:
#My powerpc compile environment
setenv CROSS_COMPILE ppc_4xx-
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
> 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:)
That's going to explore the problems in input parsing fairly well,
but layers of processing
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
> 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'
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
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 contai
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, C
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
22 matches
Mail list logo
