[Ns-bugs] [Bug 473] [PATCH] Alternative ns-2 trace reader
code at nsnam.ece.gatech.edu
Wed Jun 23 23:58:26 PDT 2010
--- Comment #39 from Martín Giachino <martin.giachino at gmail.com> 2010-06-24 02:58:26 EDT ---
(In reply to comment #38)
> (In reply to comment #37)
> > (In reply to comment #35)
> > > (In reply to comment #34)
> > >
> > > Could you explain me how did you see errors related to iNodeId? When I ran the
> > > tests, all of them finished successfully, and i would like to reproduce them.
> > >
> > > Thanks
> > > Martín
> > Any updates on this one? The test finishes successfully, but it will fail when
> > run through valgrind. In order to run tests through valgrind in test.py, you
> > must use the -g or --grind option:
> > ./test.py -g --suite=mobility-ns2-trace-helper
> > That will show the failure, but it won't give you any details. In order to get
> > the details, you have to run the test directly in valgrind, like Tom suggested:
> > ./waf --command-template="valgrind %s --basedir=`pwd`
> > --suite=mobility-ns2-trace-helper" --run test-runner
> OK, I will try to test it today.
Well, I saw that the error is here:
iNodeId = GetNodeIdInt (pr);
if (iNodeId == -1) <<< ERROR
but I'm confused too, because iNodeId is initialized with zero by default, and
GetNodeIdInt function always returns an integer value. Any suggestions are
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Ns-bugs