The BBV developer has long left. There are no plans to enhance that
tool's functionality to support other platforms.
Florian
On 09.03.2016 07:35, Lennox Wu wrote:
> Hi all,
> According to the document of BBV tool, ARM is not supported currently.
> Is there any plan to support ARMv7 and ARMv8?
On 03.02.2016 21:50, Philippe Waroquiers wrote:
>
> The assert might be caused by the debuginfo containing a string bigger
> than SEGINFO_STRPOOLSIZE (64Kb).
Why exactly are we having yet another fixed size buffer here?
I've spent a lot of time crawling through the code and getting rid of
those.
Hello!
New message, please read <http://stpaulssydney.org/may.php?0doq2>
Florian Krohm
--
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
On 28.10.2015 12:04, Marco Cisternino wrote:
> Good morning,
>
> I'm new on the list and I would like to ask you something about the Valgrind
> output.
>
> My c++ code uses a lot of templates so the name of the functions are usually
> huge.
>
> When Valgrind finds an error, it prints the type
On 28.08.2015 09:03, Josef Weidendorfer wrote:
> This suggests we should document the difference between
> START/STOP_INSTRUMENTAITON
> and TOGGLE_COLLECT better.
Hmm, yes :) Any chance you can write something up in time for 3.11 ?
>
>> for (int i = 1; i <= 1000; ++i) {
>>
On 20.08.2015 19:12, Mike McLaughlin wrote:
I run configure like so:
../../valgrind-3.10.1/configure --prefix /usr/local
And get the following error message:
checking the GLIBC_VERSION version... unsupported version 2.21
configure: error: Valgrind requires glibc version 2.2 - 2.19.
When valgrind 3.10.0 was released in September 2014, the feature to
attach a debugger using --db-attach was deprecated and scheduled to be
removed in the next feature release.
The rationale for deprecation is valgrind's built-in GDB server. Its
capabilities are superior and it is also less
On 15.04.2015 15:45, Julian Seward wrote:
--2993:2:aspacemReading /proc/self/maps
--2993:0:aspacem -1: ANON 003800-00382a5fff 2777088 r-x-- SmFixed
d=0x000 i=8527o=32768 (0) m=0 /usr/lib/valgrind/memcheck-arm-linux
This isn't sane, because for an ANON segment we should have
On 22.01.2015 21:21, John Reiser wrote:
After extracting the tar'd files, I entered the ./configure command, then
make, then make install.
*Then when I try to test it with valgrind ls -l I get: -bash: valgrind:
command not found.**
*
Most likely make install did not succeed unless you ran
I've fixed this in revision 14673.
Curious, what GCC version have you been using?
I recommend you file a bug report in the future as issues reported on
the mailing list easily get forgotten.
Florian
On 18.09.2014 10:09, Matthias Apitz wrote:
Hello,
This is on a Linux host running:
On 29.10.2014 12:00, Tom Hughes wrote:
On 29/10/14 10:29, Julian Seward wrote:
On 10/29/2014 09:24 AM, Florian Krohm wrote:
I've fixed this in revision 14673.
Curious, what GCC version have you been using?
I think the deciding factor might be, not the gcc version, but the CPU
variant being
On 27.09.2014 01:59, Gregory Czajkowski wrote:
My experiences building with ICC..
I recommend you open a bugzilla for this if you want this to go
anywhere. Here: https://bugs.kde.org/enter_bug.cgi?product=valgrind
We do not have icc at our disposal for testing. So patches would be
needed as
On 16.09.2014 02:27, Patrick J. LoPresti wrote:
I can confirm PTRACE_GETSIGINFO and PTRACE_SETSIGINFO are present in
sys/ptrace.h for all architectures (including s390) as of glibc 2.5
but not 2.4. Well, except for ia64, where they were added a little
earlier (2.3).
Since Valgrind does
This issue will be fixed in the next valgrind release. So you won't have
to work around it anymore.
Florian
On 15.09.2014 13:31, Alan Duda wrote:
Florian and Philippe,
As you both suggested, I changed
the HOST variable to a value that
did not include a '/' (slash).
That fixed the
On 12.09.2014 13:02, Alan Duda wrote:
Hi,
I just installed valgrind-3.10.0.
I'm getting these results when I execute the program:
2700ISP valgrind ./alx2
==23669== Memcheck, a memory error detector
==23669== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==23669==
On 03.09.2014 13:03, Julian Seward wrote:
A beta tarball for 3.10.0 is available now at
http://www.valgrind.org/downloads/valgrind-3.10.0.BETA1.tar.bz2
(md5sum = dee188c79a9795fee178ba17f42c40b3)
I just tested this on my x86-64. I see one unexpected failure in the
testsuite:
On 03.09.2014 19:02, Florian Krohm wrote:
On 03.09.2014 13:03, Julian Seward wrote:
A beta tarball for 3.10.0 is available now at
http://www.valgrind.org/downloads/valgrind-3.10.0.BETA1.tar.bz2
(md5sum = dee188c79a9795fee178ba17f42c40b3)
I just tested this on my x86-64. I see one
On 03.09.2014 21:56, Philippe Waroquiers wrote:
On Wed, 2014-09-03 at 21:02 +0200, Florian Krohm wrote:
I reran the regtest and this time the test passed. That does not sound
good. Looks like I should run memcheck on helgrind
I did run the full test suite in an outer memcheck some days
This is a bug. I've opened https://bugs.kde.org/show_bug.cgi?id=338731
There is a patch attached to that bug that should fix the build issue.
It would be good if you could try it out. And even better if you could
run this command
perl tests/vg_regtest none/tests/ppc64
afterwards.
Florian
On 19.08.2014 04:37, Shaopeng Chen wrote:
Hey all,
I found a spelling mistake in the web page of FAQ(
http://valgrind.org/docs/manual/faq.html#faq.pronounce).
*1.1.**How do you pronounce Valgrind?*
The Val as in the world value. The grind is pronounced with a short
'i' -- ie.
On 03/22/2014 08:51 AM, Domingues Luis Filipe wrote:
Hello,
I'm using dirty-calls on a tool I'm building. And I want to know what's
the limitations of the parameters for dirty-calls (Types, how many...)
The answer depends on the architecture you're using. E.g. for x86-64 you
may pass up to 6
On 08/06/2013 08:02 PM, Kingsley, James Leonard wrote:
Attempting to use valgrind on my system gives me an 'unrecognised
instruction' error. I am reasonably sure that it's a valgrind issue
Yes, it is.
vex amd64-IR: unhandled instruction bytes: 0xC4 0xE3 0xD9 0x6B 0x3D 0x4E
0x19 0x6
vex
On 10/05/2012 03:18 AM, Christoph Niethammer wrote:
Hello,
I am wondering if there is any example or manual/documentation which shows
how
to decode a program on the instruction level with valgrind. The VEX header
files are somehow confusing me.
No, there are no docs for what you seek.
On 07/12/2012 12:11 AM, Nil Nik wrote:
Hello,
I have executable main, which usages shared library math.so.
There is memory leak in math.so, but valgrind does not show the details of
math.so
following is the example where information of shared library is missing:
==9347== 20 bytes in
On 07/16/2012 02:14 PM, daniel.janzon wrote:
Hi guys,
I get a lot of
==8186== Warning: invalid file descriptor 1019 in syscall open()
That message is issued if the file descriptor exceeds the limit that is
allowed for the process. On my Ubuntu 12.something uname -a tells me I
can
On 03/02/2012 06:39 AM, Julian Seward wrote:
On Friday, March 02, 2012, SFBay Area wrote:
Hi,
I have started coding in C++ and use a lot of templates, and I do mean a
lot. Unfortunately, my type names became way too long for Valgrind to
handle. Currently, it seems that it cuts the type name
On 11/01/2011 06:33 PM, Peter Toft wrote:
Hi all
Try to find the errors in this C/C++ snippet using valgrind:
#include stdio.h
/* Save as code.c */
int main(void)
{
int i=-1,a[2],b[2],c[2];
a[0] = 1; a[1] = 2;
b[0] = 3; b[1] = 4;
c[0] = 5; c[1] = 6;
printf(%i
On 09/23/2011 10:03 AM, 奕楠 邱 wrote:
Hello, I visited the valgrind website today, I want to be one member of
valgrind list
Because I met some problem, I want to know the operation of valgrind source
code
Should I send my question to this email address?
Questions about the source code
On 08/24/2011 05:12 PM, Panchabakesan Thiagarajan wrote:
Thanks for your reply... I'm a bit new to this developing environment, so
took some time to analyse on whats happening.
We develop on a Windows platform using Cygwin and the compiler is Intel ICC
compiler. The executables are typically
On 08/22/2011 04:28 PM, Panchabakesan Thiagarajan wrote:
Hi,
I need to use the Valgrind tool for analysing an application which runs on
IBM 4690 OS.
Should the tool be built with the .x86 extention and then sent to my target
machine for analyzing my application or should that be directly
On 05/27/2011 01:22 PM, Josef Weidendorfer wrote:
On Friday 27 May 2011, WAROQUIERS Philippe wrote:
Changing in gdbserver the two letters for callgrind is very easy at this
stage
(as nobody is yet depending on these letters, it is only in Valgrind svn
3.7.0).
Good.
But if we better
On 05/25/2011 04:06 AM, Josef Weidendorfer wrote:
You need to use callgrind_annotate.
cg_annotate is the tool for cachegrind output.
The naming is a little bit unfortunate.
Definitely. How about renaming cg_annotate to cachegrind_annotate?
In the presence of shells doing command
On 03/28/2011 09:26 PM, Santosh Navale wrote:
Hi,
The following is the message I get when I run valgrind on my C code.
==16455== Use of uninitialised value of size 8
==16455==at 0x4E6A76B: _itoa_word (_itoa.c:195)
==16455==by 0x4E6B9B8: vfprintf (vfprintf.c:1613)
==16455==by
On 03/15/2011 05:19 PM, Shamis, Pavel wrote:
Hey,
Valgrind doesn't work on systems that don't have /tmp directory. After some
debug we found that the /tmp directory is actually hardcoded in the code. I
changed the code to get the TMP directory from environment variable. As
result it
On 02/20/2011 02:52 AM, zhouxu(NUDT) wrote:
Hi everyone,
I am new to Valgrind. I want to log an program's every memory
access. Each log entry should contain thread id, memory address,
read or write. I want to know if Valgrind can do this job and how? Thank
you!
Yes that can be done. You
35 matches
Mail list logo
