guy keren wrote:
int i;
int j = i;
int k = j;
if (k > 0) blablabla...
valgrind will only point the last one as an error (at least, that's how it
is in valgrind-1.0.3).
Actually, that's intentional. Otherwise, consider the following example:
struct padding {
char a;
int b;
} struct a, b;
.
On Wed, 26 Jan 2005, Orna Agmon wrote:
> On Wed, 26 Jan 2005, guy keren wrote:
> > On Mon, 24 Jan 2005, Orna Agmon wrote:
> >
> > > Valgrind is not always correct. It sometimes reports errors which do not
> > > exists - they have no reason to exist and other memory checkers (such as
> > > third)
On Wed, 26 Jan 2005, guy keren wrote:
> On Mon, 24 Jan 2005, Orna Agmon wrote:
>
> > Valgrind is not always correct. It sometimes reports errors which do not
> > exists - they have no reason to exist and other memory checkers (such as
> > third) do not find them.
>
> that, ofcourse, is no proof - t
On Mon, 24 Jan 2005, Orna Agmon wrote:
> Valgrind is not always correct. It sometimes reports errors which do not
> exists - they have no reason to exist and other memory checkers (such as
> third) do not find them.
that, ofcourse, is no proof - the other checker might be too limited, or
have a
On Mon, 24 Jan 2005, Yedidyah Bar-David wrote:
> Aviv, nobody thought that modern C++ compilers/OSes can't compile/run
> this piece of code. The bug is obviously elsewhere in your program. Now,
> traditionally, it would be hard to debug - you'd, as someone else
> suggested, find a minimal subset of
On Mon, Jan 24, 2005 at 11:12:28AM +0200, Aviv Goll wrote:
> On Mon, 24 Jan 2005 05:16:23 +0200, Micha Feigin <[EMAIL PROTECTED]> wrote:
> > At Mon, 24 Jan 2005 02:45:52 +0200,
> > Aviv Goll wrote:
> > >
> > > hi,
> > > I'm currently writing an assignment in c++ using g++.
> > > according to some
On Mon, 24 Jan 2005 05:16:23 +0200, Micha Feigin <[EMAIL PROTECTED]> wrote:
> At Mon, 24 Jan 2005 02:45:52 +0200,
> Aviv Goll wrote:
> >
> > hi,
> > I'm currently writing an assignment in c++ using g++.
> > according to some printouts, during the following lines:
> >
> > stringstream Fstr;
> > fs
Quoting Aviv Goll <[EMAIL PROTECTED]>:
You better fix all vargrind errors. It takes time to understand
why they are happening. The stability of my applications have bin
raised significantly high after fixing all vargrind errors.
Additional thing to test in valgring is gracefull shutdown of
you ap
At Mon, 24 Jan 2005 02:45:52 +0200,
Aviv Goll wrote:
>
> hi,
> I'm currently writing an assignment in c++ using g++.
> according to some printouts, during the following lines:
>
> stringstream Fstr;
> fstr<<"blah blah";
>
Just tried running just that and had no problem. Do notice that in the
hi,
I'm currently writing an assignment in c++ using g++.
according to some printouts, during the following lines:
stringstream Fstr;
fstr<<"blah blah";
the seconed line creates a sigmentation fault.
other lines in the project doesn't create such a sig. fault and even
more weird is that I uplo
10 matches
Mail list logo
