the *first* access to a line
causes a miss. These are sometimes called mandatory misses. A large cache
*will* eliminate *capacity* misses.
HTH -- Eliot Moss
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourcef
a
system call that valgrind does not recognize? One would need to know
register contents to go further with that.
Btw, naming a program "test" is not necessarily a wonderful idea if
the current directory happens to be on your path, since "test" is a
program often used by s
e had if the
executable had the information kept with it and not stripped.
Best - Eliot Moss
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
On 2/8/2023 4:10 PM, SAI GOVARDHAN M C PES1UG19EC255PESU ECE Student wrote:
Hi,
We are students working on memory access analysis, using the Lackey tool in
Valgrind.
Our memory trace results in a large log file, and we need the trace from discrete points of
execution (between 40-60%).
Instead
On 1/30/2023 7:08 AM, Ivica B wrote:
Can you please share the instructions on how to do it?
On Sun, Jan 29, 2023, 9:07 PM Eliot Moss mailto:m...@cs.umass.edu>> wrote:
I have used lackey to get traces, which I have fed into
a cache model to detect conflicts and such. You could
I have used lackey to get traces, which I have fed into
a cache model to detect conflicts and such. You could
also start with the lackey code and model the cache model
into the tool (which a student of mine did at one point).
Regards - Eliot Moss
grind?
The lackey tool does just that - output a trace of memory references.
-- Eliot Moss
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
On 1/14/2021 9:35 AM, Geoff Alexander wrote:
I wonder if this is related to Valgrind bug 439542 Cannot compile valgrind on Ubuntu 20.04 docker
due to failed compilation libmpiwrap.c (https://bugs.kde.org/show_bug.cgi?id=420518).
Geoff Alexander, Ph.D.
Software Engineer, Corporate Tools Developm
onfiguring --without-mpicc or else revert the MPI version to 2.something instead of
3.something. (The latter is a little bit of a guess, but because configure --help mentions MPI2.)
HTH - Eliot Moss
___
Valgrind-users mailing list
Valgrind-users@lists.s
;how to do something on
linux" thing ...
Maybe somebody can think of even nicer ways to do this.
Regards - Eliot Moss
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
improper freeing or lack of initialization of pointers ...
Regards - Eliot Moss
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
A0BEF
> -
> $ gcc -c foo.s
> $ gdb foo.o
> (gdb) x/i 0
> 0: vcvt.f64.s32 d0, d0, #1
> (gdb)
If we are really talking about the ARM processor, this
r of instructions and variants on them.
Valgrind covers *most* of them, but this means that this particular instruction
it does not recognize.
It's a moving target -- new models and new instruct
You can get a trace of memory accesses from lackey. You would need to process
it down a bit if all you want is counts and if you want to sort it by location,
but it would be reasonably easy to do that.
Eliot Moss
On October 30, 2014 1:36:14 PM EDT, David Goldsmith
wrote:
>Hi,
>is
On 9/26/2014 12:38 PM, Julian Seward wrote:
> On 09/25/2014 12:52 PM, Eliot Moss wrote:
>> I started updating the valgrind documentation to add description
>> of this new feature, and expect to submit a patch soon for
>> developer approval.
>
> https://bugs.kde.org/show
On 9/25/2014 5:45 AM, Skarakis, Konstantinos wrote:
> That's fantastic. Thank you very much for your time. It works great.
>
> Here's how I am using it:
>
> I have this line in my ~/.valgrindrc:
>
> --log-file=/software/valgrind/rpts/%s{"/software/dstring"}-%p-report.txt
>
> And these are the conte
On 9/25/2014 5:45 AM, Skarakis, Konstantinos wrote:
> That's fantastic. Thank you very much for your time. It works great.
Good news that it works for someone else too!
I started updating the valgrind documentation to add description
of this new feature, and expect to submit a patch soon for
deve
On 9/24/2014 7:39 AM, Eliot Moss wrote:
On 9/24/2014 5:31 AM, Skarakis, Konstantinos wrote:
Ok -- I decided to just give it a try in a copy of valgrind
updated to svn head. The issue is that I was temporarily
sticking a null character into the format string, yet the
format string was declared
odifying 'format' in place, the code needs to copy the
relevant part out to a separate string. Also, some of the routines I called
in the code (execva, sigaction, strlen) seem not to have their proper
declarat
f the invoking valgrind will be the script's
PPID, etc.
If the "powers that be" think this might be
generally useful, then let me know how you would
prefer to receive the patch, and any tidying you
feel would be in order ...
Regards -- Eliot Mos
if this
part of the code has not been changed a lot, then the patch should
not be too bad to extract.
I've been meaning to submit it for some time, actually, and this is
a good prompt to make me do it!
Regards -- Eliot Moss
It appears to me that the compiler is writing
to all bytes of the string in a loop, as opposed
to simply writing a 0x0 to the first byte.
Regards -- Eliot Moss
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http
bug.
You might want to verify that valgrind and your code have the same
notion of what the malloc/free routines are, etc., i.e., that valgrind
is able to hook into all allocation and freei
On 7/8/2014 3:47 PM, Karl Cronburg wrote:
> On 07/08/2014 02:48 PM, Philippe Waroquiers wrote:
>> On Tue, 2014-07-08 at 14:39 -0400, Eliot Moss wrote:
>>> On 7/8/2014 2:04 PM, Philippe Waroquiers wrote:
>>>> On Tue, 2014-07-08 at 03:49 -0400, Karl Cronburg wrote
On 7/8/2014 2:04 PM, Philippe Waroquiers wrote:
> On Tue, 2014-07-08 at 03:49 -0400, Karl Cronburg wrote:
I can confirm that Jikes RVM does it own special allocation
of stacks, which might be involved here.
I am wondering why anyone would think a tool like memcheck
would work with a Java virtual
On 5/14/2014 2:21 PM, Rob Taylor wrote:
> Thank you Milian Wolff and Eliot Moss,
Typical users of tools like valgrind have more background in
how all this works -- not a criticism of you, just a difference
in expectation.
The volume of code that results from compiling a program
consisting o
ams using the same library. There's a lot of
mechanism there, even if you are not using much of it, and
even if you are using parts of it without realizing it ...
Regards -- Eliot Moss
--
"Accelerate Dev Cycles with A
g more like malloc/free underneath, but
even then it might not be appropriate.
Regards -- Eliot Moss
--
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
heck len > 0 *before* accessing
in[len - 1].
The still-reachable blocks mystify me a little. The only one
I see is the last IntIn, since players is freed and the rest
won't be reachable from any accessible variable.
Of course there a
If you expect no more than one \n in the string, then strchr may be
what you want, or strrchr to find the last \n regardless. If they
return non-null, you can examine the next byte to see if it is \0
and then clear th
It's always nice to have additional cases covered.
May I gently suggest that if an 8-bit case is added,
the 16-bit case also be added at the same time? :-)
Regards -- Eliot Moss
Original Message
Subject: [Valgrind-developers] vex: r2532: Fix PCMPxSTRx variant $0x46.
ttp://www.valgrind.org/downloads/repository.html
Of course, if you prefer using git, you can do
git svn clone ...
Regards -- Eliot Moss
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's secur
yond causing a signal, which presumably is
unhandled here). A quick look suggests that this is a PADDB instruction.
I think someone has been working on adding some of those instructions
latelt; it *might* be covered if you grab and
e a bit. You can kind of think of it as
like a somewhat optimized interpreter for your machine --
but it is still at some level an interpreter.
So, a 10x slowdown is *good*, not bad, given what is going on
under the covers.
Eliot Moss
--
currency.
> Thanks for your answer in advance.
No problem.
Eliot Moss
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
've not looked for that
information, but system call tracing in valgrind certainly
prints it, so it should not be hard to get.)
Regards -- Eliot Moss
--
This SF email is sponsosred by:
Try Windows Azure free for 90 da
I'm not super-familiar with this part of the code,
but I wonder if the insertion you put in syswrap-generic.c
needs to be in syswrap-linux.c, to match where you
put things in syswrap-linux.h ...
Eliot Moss
--
Try b
nd why it
fails unless if was added since you checked out from SVN.
Best wishes -- Eliot Moss
--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cl
algrind. See the
man page :-) ...
Best wishes -- Eliot Moss
--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on all
On 2/14/2012 6:12 PM, Julian Seward wrote:
>> So ... I am running tests with the decoder revised to allow 0x66 on the fpu
>> instructions.
>> Does anyone know of a reason why doing this would be bad/wrong?
> Giving a blanket OK for 0x66 on FPU instructions makes me nervous, that we
> might inadv
In my continuing quest to get the HotSpot Java
virtual machine to work under valgrind, I found
that it wants to execute this opcode:
0x66 0xDD 0x4
This is (as far as I have been able to determine)
a floating point load (fldl) with a 0x66 size
prefix. Now the size prefix is useless with this
instr
I was wrong :-( ...
0x66 0x0F 0x3A 0xDF appears to be AESKEYGENASSIST.
Someone else will have to address that (if at all).
Sorry ... Eliot
--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing make
et
back within a day. Perhaps someone else can verify it.
If this variant is close enough to existing ones, I *might*
be able to add it to what I am patching
Regards -- Eliot Moss
--
Virtualization & Cloud Managem
On 2/7/2012 5:13 PM, Julian Seward wrote:
I'm clear about the 2 repos business now :-) ...
>> 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 und
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-lev
On 2/4/2012 7:02 AM, Julian Seward wrote:
>
>> I did that, but when I run the updated valgrind on
>> the same program as before (Oracle's HotSpot JVM),
>> it fails on a 0xF 0xAE 0x3F instruction, which
>> appears to be either a CLFLUSH or an SFENCE (both
>> decode the same way in the docs, so I am
e a significant project to support
a range of guest processor capabilities controlled
with flags, etc.
Regards -- Eliot Moss
--
Try before you buy = See our experts in action!
The most comprehensive online learning librar
On 1/31/2012 4:15 AM, Julian Seward wrote:
>
> (You didn't reply-all on this; I assume that was intended)
I did; thanks ...
>> Your comments on the probable (non)utility of the instruction are
>> suggestive as to why the copied-over x86 code is commented out.
>> Unsurprisingly, simply uncommentin
On 1/30/2012 3:29 AM, Julian Seward wrote:
> I would have thought that FSAVE/FRSTOR in 64 bit mode is essentially
> useless, and the fact that we've not so far needed to implement them
> kind of supports that suspicion. Reason is that they don't save or
> restore the XMM registers. The x86-64 bi
tSpot on DaCapo
benchmarks fail under valgrind because this instruction is
missing.
Could someone perhaps clarify whether it simply hasn't been
done or if there is some deeper reason why the code was
commented out?
Regards -- Eliot Moss
PS -- I did search the archives on these but fai
50 matches
Mail list logo
