On 2/7/2012 5:19 AM, Julian Seward wrote:

Thank you, Julian, for your patient instructions :-) ...

> # merge any other changes that happened in the meantime
> cd VEX
> svn up
> cd ..

Why only VEX? I also added tests in none/test/amd64.
Is there some reason to avoid svn up in the valgrind
top-level directory?

> # remake, re-test
>
> # generate diff
> cd VEX
> svn diff -rHEAD
>
> # send the diff

That's clear enough, but are you saying you want the
tests as a separate patch?

> One thing though.  Bugs discussed on mailing lists tend to get
> forgotten or otherwise fall through the cracks.  A much more reliable
> approach, if you have bugs/patches in future, is to file a bug as
> described at http://valgrind.org/support/bug_reports.html
> and do all the discussion, patches, patch reviewing etc in the bug
> report.

Right.  I'll put in a bug report before submitting the
patch. I hope to get to all this within a week (a big
thing happening at work is draining any "spare" cycles).

I'll post the other missing instruction as a bug report
too.  I am also on the trail of something that looks like
an unimplemented (or differently implemented?) system call.
The Java program under test, which is the DaCapo eclipse
benchmark, complains that it can't create the workspace
it's going to work on, throws an exception, and quits.
There is no valgrind complaint. However, if I run the
benchmark without valgrind, it completes normally.

Does valgrind restrict the number of open files? I noticed
that the benchmark had over 50 files open, and might have
hit a limit if it is set at 64 or something.

My next step is to compare trace output without valgrind
to valgrind --trace-syscalls=yes and see where the system
calls majorly diverge.  Of course it could be something
else, but ...

I also have one run that just core dumps. No valgrind
end-of-run stuff, no complaint, just a core dump. I
am scratching my head a bit on how to dig in on that
one, since it seems to have jumped to address 0 and
I don't get stack back trace ... but maybe I am
being simple-minded about how I use gdb on this ...

Is there a way to file a bug report with a core dump?

Regards -- Eliot

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to