On Wed, Apr 21, 2010 at 5:40 AM, Jorge Moraleda wrote:
> >> Hello Jorge,
> >>
> >> Unfortunately not all libraries have been designed with data-race
> >> detection tools in mind. Several libraries contain code that triggers
> >> benign data races. Examples are the I/O code in libstdc++ and in libc
>> Hello Jorge,
>>
>> Unfortunately not all libraries have been designed with data-race
>> detection tools in mind. Several libraries contain code that triggers
>> benign data races. Examples are the I/O code in libstdc++ and in libc.
>>
>> You can either create a suppression pattern to suppress th
On Tue, Apr 20, 2010 at 2:18 PM, Stefano Sabatini wrote:
> Hi all,
>
> I'm currently using valgrind-3.5.0-Debian.
>
> I see in the commentary:
> ...
> ==7197==by 0x80688A3: XYZ::Foo::Bar() (FooBar.cxx:361)
> ==7197==by 0x4326435: PThread::PX_ThreadStart(void*)
> (tlibthrd.cxx:1341)
> ==719
This should be tuned in gcc, not Valgrind. Valgrind just prints the
debug info generated by gcc.
For example:
$ cat leak.cc
int foobar() {
int *foo = new int;
delete[] foo;
return 0;
}
int main() {
foobar();
return 0;
}
$ g++ ../leak/leak.cc -o leak -g
$ valgrind ./leak
...
==11525== Mi
AFAIK Valgrind currently runs on ARMv7, but supports only ARMv5
instruction set (plus several v6 and v7 instructions).
On Tue, Apr 20, 2010 at 6:54 AM, raja gobi wrote:
> Hi all,
>
> I saw that valgrind is now available for ARM/Linux in trunk which is great.
>
> Read on the mozilla developers pag
Hi all,
I'm currently using valgrind-3.5.0-Debian.
I see in the commentary:
...
==7197==by 0x80688A3: XYZ::Foo::Bar() (FooBar.cxx:361)
==7197==by 0x4326435: PThread::PX_ThreadStart(void*) (tlibthrd.cxx:1341)
==7197==by 0x4042584: start_thread (pthread_create.c:300)
==7197==by 0x47
