Tom Hughes [mailto:t...@compton.nu]
eyurt...@abo.fi wrote:
However it is possible to pack the structs without holes...
You're going to recompile glibc and all the other libraries that your
program uses with that option are you?
And, of course, if you don't, structs passed between packed and
You are right, I tried to recompile everything and the compilation of
standard c++ libraries etc. fail. Sorry for wasting your time I guess
:(
If you want to persist with this idea, don't let me stop you from
starting
work on making everything capable of building with packed structures. It
1. How can I find out how much memory is used in each object in firefox?
2. How can I find out what are the functions spent the most time during my
program execution?
Valgrind is not an all-purpose tool. It does not do either of those things.
==2616== Thread 4:
==2616== Invalid read of size
They indicate that valgrind's memory manager was asked to
handle a block (actually a single contiguous address
interval, which could be a block or a non-block) of more
than 100,000,000 bytes ... on x86_64 with 64-bit addresses
and much more latitude for placement of PT_LOAD, this
might
We have adopted Valgrind as a periodic QA measure: every six months,
we run all our tests through it. This takes a couple of months for
everything to run, so we don't feel we can do it more often. What
it finds for us is uninitialized variable errors; our internal memory
management takes big
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
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,
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't
Street, Cambridge, CB2 1DP
United Kingdom
Tel: +44-1223-371554
john.dall...@siemens.com
www.siemens.com/plm
-Original Message-
From: Ildar Isaev [mailto:iis...@ispras.ru]
Sent: Wednesday, May 26, 2010 4:08 PM
To: Dallman, John
Cc: valgrind-users@lists.sourceforge.net
Subject: Re
I don't have any trouble with FP math on 32-bit x86, but I take
a different strategy from you.
I set the x87 FP unit to use 64-bit doubles rather than 80-bit
doubles, since that makes the results far more similar to 64-bit
Linux, and other platforms that use 64-bit doubles. 32-bit Linux
uses
Use --num-callers=25, or any other number. This is in valgrind --help,
but isn't specific to memcheck.
best,
--
John Dallman
Parasolid Porting Engineer
Siemens Product Lifecycle Management Software
Industry Sector
46 Regent Street, Cambridge, CB2 1DP
United Kingdom
Tel: +44-1223-371554
Benjamin Schindler [mailto:bschind...@inf.ethz.ch] wrote:
... the backtrace size used by valgrind is too small... i.e. it
just shows 10 functions. Is there a way to see more than just that
Use the --num-callers=number command line switch.
best,
--
John Dallman
Parasolid Porting Engineer
there is a multicore platform named tile64 http://en.wikipedia.org/wiki/TILE64
Now, I want to let valgrind execute onto this platform, does anyone know the
exact way?
TILE64 uses a MIPS-based instruction set. The platforms page on the Valgrind
website,
John Reiser [mailto:jrei...@bitwagon.com] wrote:
I'm having an issue with valgrind - mine regression takes 4 hours instead
of 45 mins when run in valgrind.
An elapsed time ratio of 240:45 (5.3 : 1) is not unusual, and may be better
than average.
That's definitely better than I see: I'm
Because the recompilation time of one patched php is nearly 20 seconds, so if
the
sum of degradation time is more than 20 seconds, then our method of
indirecting
function will perorm worse than native regression
testingapp:ds:%20%20regression%20testing.
You must expect performance under
Julian Seward [mailto:jsew...@acm.org] wrote:
Even then it's not simple. The x87 control word has a bit-pair that
controls the default x87 FP precision. Currently V ignores all attempts to
change it, and just does its thing at 64 bits. If 80-bit arithmetic
becomes supported, and V ignores
Do any common platforms, other than x86/x86_64, offer more-than-64-bit long
double?
Not that they support as full speed hardware operations, AFAIK. SPARC has
defined
registers and instructions for 128-bit floating point, but implements them as
sequences of operations on 64-bit floats, so they
I'm looking at using callgrind to replace an expensive Windows coverage tool,
and for some other work where the ideas are only part-formed.
The default callgrind run and callgrind_annonate display shows Ir events, but
I only need to count function entries. Is there a way to only collect those
and
Julian Seward wrote:
I suspect not. In any case counting insns is not terribly expensive,
so the gain you'd get would be modest.
OK.
I suspect the names are present in the callgrind.out file, and so
callgrind_annotate just slices out those that you list. It doesn't
itself know the names.
Philippe Waroquiers philippe.waroqui...@skynet.be wrote:
Starting callgrind with default options, and then using
kcachegrind on the resulting callgrind.out file, kcachegrind
shows the nr of calls to the functions.
I'm trying to avoid using kcachegrind, because I need to automate
this process.
I have a lot of calls to functions with names that I recognise,
but which have a '2 appended to their names. These don't exist
in the source: any idea what they signify?
They're in the callgrind documentation; they're about recursion, and
I clearly need to accumulate their call counts into
Julian Seward wrote:
One other option is to play around with optimisation settings for your app,
to see if it changes g++'s inline/no-inline decisions.
g++'s -fno-inline option may help, although it has the same limitation of not
applying to libraries.
--
John Dallman
-
> I've got a program which seems to cause heap corruption so I thought valgrind
> would be
> able to tell me where this occurs. The trouble is the program uses data files
> from the
> running directory for configuration purposes and running the program under
> valgrind
> seems to prevent it
I'm starting to look at fuzz testing the mathematical modelling library I work
on, which reads complicated data files that are produced by end-users, and
could plausibly be used to stage buffer overflow attacks. The basics obviously
come first: use -fstack-protector, take care with string
> Whilst 3.12.0 continues to support the 32-bit x86 instruction set, we would
> prefer users to migrate to 64-bit x86 (a.k.a amd64 or x86_64) where possible.
Sound move. I was able to give up shipping 32-bit x86 Mac and Linux software
earlier this year, and our customers tend to be quite
dustry Sector
Siemens Industry Software Limited
Francis House, 112 Hills Road,
Cambridge CB2 1PH, United Kingdom
Tel. :+44 (1223) 371554
Fax :+44 (1223) 371700
john.dall...@siemens.com
www.siemens.com/plm
-Original Message-
From: FEVOTTE Francois [mailto:francois.fevo...@edf.fr]
S
This is potentially interesting for what I do. Is the documentation at
http://edf-hpc.github.io/verrou/vr-manual.html up to date?
Something that would be very useful would be control of the seed of the random
number generator, so that we could repeat and debug cases that gave strange
results.
ills Road,
Cambridge CB2 1PH, United Kingdom
Tel. :+44 (1223) 371554
Fax :+44 (1223) 371700
john.dall...@siemens.com <mailto:john.dall...@siemens.com>
www.siemens.com/plm
From: [ext] Dallman, John [mailto:john.dall...@siemens.com]
Sent: Thursday, June 01, 2017 12:29 PM
To: 'Ivo
> As a Valgrind user, I see few ways to get different results with valgrind :
Another possibility is that the OP has a memory management bug, and the
inevitably slightly different memory layout when running under Valgrind can
trigger it. I have not seen this with Valgrind, but I have seen it
The memory requirement for Valgrind is “several times as much memory as the
application you’re testing needs without Valgrind.”
How much memory does your application use normally?
--
John Dallman
From: Padala Dileep [mailto:padala.dil...@gmail.com]
Sent: 25 January 2019 10:00
To:
> However, I've also been told that the g++ compiler will initialize all stack
> objects to zero when compiling for debug (the -g option). Yet, valgrind
> still detects the un-init condition.
I think whoever told you that was confusing it with Microsoft Visual Studio.
The default debug-build
NDK23c does not provide any libgcc libraries. This is reasonable, since it also
does not provide a gcc: it uses clang instead. I’ve never tried to build
Valgrind for Android, but hopefully someone else can tell you how to do it with
a modern NDK.
--
John Dallman
From: $rik@nth
Sent: 23 June
32 matches
Mail list logo
