|
From: Alessandro B. <a.b...@ev...> - 2010-08-11 08:07:56
|
Hi, I build valgrind on my x86 system. Now I'd like to make some tests in valgrind for see that all is ok. There are, in valgrind, some tests to execute for validate installation? Thanks. Best Regards. |
|
From: WAROQUIERS P. <phi...@eu...> - 2010-08-11 08:14:35
|
In the valgrind directory, do make regtest You can also do make perf see README_DEVELOPPERS in valgrind directory for more info. >-----Original Message----- >From: Alessandro Biasci [mailto:a.b...@ev...] >Sent: Wednesday 11 August 2010 09:50 >To: val...@li... >Subject: [Valgrind-users] Execute tests in Valgrind > >Hi, > >I build valgrind on my x86 system. Now I'd like to make some tests in >valgrind for see that all is ok. > >There are, in valgrind, some tests to execute for validate >installation? > >Thanks. >Best Regards. > >--------------------------------------------------------------- >--------------- >This SF.net email is sponsored by > >Make an app they can't live without >Enter the BlackBerry Developer Challenge >http://p.sf.net/sfu/RIM-dev2dev >_______________________________________________ >Valgrind-users mailing list >Val...@li... >https://lists.sourceforge.net/lists/listinfo/valgrind-users > ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Alessandro B. <a.b...@ev...> - 2010-08-11 08:28:26
|
Thanks! It is possible to compile only the C test and not C++? Thanks a lots. On 11/08/2010 10:15, WAROQUIERS Philippe wrote: > In the valgrind directory, do > make regtest > > You can also do > make perf > > see README_DEVELOPPERS in valgrind directory for more info. > > > > >> -----Original Message----- >> From: Alessandro Biasci [mailto:a.b...@ev...] >> Sent: Wednesday 11 August 2010 09:50 >> To: val...@li... >> Subject: [Valgrind-users] Execute tests in Valgrind >> >> Hi, >> >> I build valgrind on my x86 system. Now I'd like to make some tests in >> valgrind for see that all is ok. >> >> There are, in valgrind, some tests to execute for validate >> installation? >> >> Thanks. >> Best Regards. >> >> --------------------------------------------------------------- >> --------------- >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Valgrind-users mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-users >> >> > ____ > > This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. > > Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. > > Any views expressed in this message are those of the sender. > |
|
From: WAROQUIERS P. <phi...@eu...> - 2010-08-11 08:34:49
|
>From: Alessandro Biasci [mailto:a.b...@ev...]
...
>It is possible to compile only the C test and not C++?
Not that I know of.
But you can try to cheat by either redefining a gcc hiding the
standard gcc, and that would create a dummy .o when it compiles
a .cpp extension or replace all .cpp files by an empty main () {}.
But why do you want to avoid running the C++ tests ?
____
This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.
Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.
Any views expressed in this message are those of the sender.
|
|
From: Alessandro B. <a.b...@ev...> - 2010-08-11 08:41:46
|
On 11/08/2010 10:35, WAROQUIERS Philippe wrote:
>> From: Alessandro Biasci [mailto:a.b...@ev...]
>>
> ...
>
>> It is possible to compile only the C test and not C++?
>>
> Not that I know of.
> But you can try to cheat by either redefining a gcc hiding the
> standard gcc, and that would create a dummy .o when it compiles
> a .cpp extension or replace all .cpp files by an empty main () {}.
>
> But why do you want to avoid running the C++ tests ?
>
Because I haven't a running C++ compiler for my platform in this moment.
Only gcc compiler works well.
> ____
>
> This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.
>
> Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.
>
> Any views expressed in this message are those of the sender.
>
|
|
From: Alessandro B. <a.b...@ev...> - 2010-08-11 09:02:39
|
On 11/08/2010 10:41, Alessandro Biasci wrote:
> On 11/08/2010 10:35, WAROQUIERS Philippe wrote:
>
>>> From: Alessandro Biasci [mailto:a.b...@ev...]
>>>
>>>
>> ...
>>
>>
>>> It is possible to compile only the C test and not C++?
>>>
>>>
>> Not that I know of.
>> But you can try to cheat by either redefining a gcc hiding the
>> standard gcc, and that would create a dummy .o when it compiles
>> a .cpp extension or replace all .cpp files by an empty main () {}.
>>
I compile valgrind first on my x86 pc (with linux) with this steps:
$ ./autogen.sh
$ ./configure --prefix=/home/valgrind/x86Install/ --disable-tls
--enable-only32bit
$ make --quiet
$ make install
$ make --quiet regtest
This is the report:
== 511 tests, 474 stderr failures, 1 stdout failure, 0 post failures ==
The test fails for stderr but if I execute a test (es: memcheck/tests$
./addressable) it pass.
Some helps?
Thanks
>> But why do you want to avoid running the C++ tests ?
>>
>>
> Because I haven't a running C++ compiler for my platform in this moment.
> Only gcc compiler works well.
>
>> ____
>>
>> This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.
>>
>> Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.
>>
>> Any views expressed in this message are those of the sender.
>>
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
|
|
From: Alessandro B. <a.b...@ev...> - 2010-08-11 13:12:03
|
On 11/08/2010 15:06, WAROQUIERS Philippe wrote:
>
>
>> The difference between the expected stderr and the optained stderr is:
>>
>> +.text Section.
>> +.data Section.
>> +.text Section.
>> +.data Section.
>> +.text Section.
>> +.data Section.
>> +.text Section.
>> +.data Section.
>> +.text Section.
>> +.data Section.
>> +.text Section.
>> +.data Section.
>>
> I have no idea where this is coming from.
>
> What is the platform you are working on (cpu, OS) ?
>
I have compile valgrind for x86. I have a Core2 Duo with Ubuntu 10.04
LTS OS.
For addressable test I have this stderr output:
.text Section.
.data Section.
.text Section.
.data Section.
.text Section.
.data Section.
.text Section.
.data Section.
.text Section.
.data Section.
.text Section.
.data Section.
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
total heap usage: ... allocs, ... frees, ... bytes allocated
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Unaddressable byte(s) found during client check request
at 0x........: test2 (addressable.c:48)
by 0x........: main (addressable.c:125)
Address 0x........ is not stack'd, malloc'd or (recently) free'd
Invalid write of size 1
at 0x........: test2 (addressable.c:51)
by 0x........: main (addressable.c:125)
Address 0x........ is not stack'd, malloc'd or (recently) free'd
Process terminating with default action of signal N (SIGSEGV or SIGBUS)
Bad memory (SIGSEGV or SIGBUS) at address 0x........
at 0x........: test2 (addressable.c:51)
by 0x........: main (addressable.c:125)
If you believe this happened as a result of a stack
overflow in your program's main thread (unlikely but
possible), you can try to increase the size of the
main thread stack using the --main-stacksize= flag.
The main thread stack size used in this run was ....
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
total heap usage: ... allocs, ... frees, ... bytes allocated
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
total heap usage: ... allocs, ... frees, ... bytes allocated
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Process terminating with default action of signal N (SIGSEGV or SIGBUS)
Bad memory (SIGSEGV or SIGBUS) at address 0x........
at 0x........: test4 (addressable.c:74)
by 0x........: main (addressable.c:125)
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
total heap usage: ... allocs, ... frees, ... bytes allocated
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Uninitialised byte(s) found during client check request
at 0x........: test5 (addressable.c:85)
by 0x........: main (addressable.c:125)
Address 0x........ is not stack'd, malloc'd or (recently) free'd
Uninitialised byte(s) found during client check request
at 0x........: test5 (addressable.c:91)
by 0x........: main (addressable.c:125)
Address 0x........ is not stack'd, malloc'd or (recently) free'd
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
total heap usage: ... allocs, ... frees, ... bytes allocated
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
Use --track-origins=yes to see where uninitialised values come from
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
total heap usage: ... allocs, ... frees, ... bytes allocated
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
This is the diff file with the expected one:
--- addressable.stderr.exp 2010-07-23 10:10:00.683997929 +0200
+++ addressable.stderr.out 2010-08-11 14:32:06.083054951 +0200
@@ -1,4 +1,16 @@
+.text Section.
+.data Section.
+.text Section.
+.data Section.
+.text Section.
+.data Section.
+.text Section.
+.data Section.
+.text Section.
+.data Section.
+.text Section.
+.data Section.
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
I use the current trunk of valgrind.
> Philippe
>
> ____
>
> This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.
>
> Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.
>
> Any views expressed in this message are those of the sender.
>
|
|
From: WAROQUIERS P. <phi...@eu...> - 2010-08-11 09:17:16
|
>This is the report: >== 511 tests, 474 stderr failures, 1 stdout failure, 0 post failures == > >The test fails for stderr but if I execute a test (es: memcheck/tests$ >./addressable) it pass. To run one test, you must do something like: perl tests/vg_regtest memcheck/tests/addressable (the test is not the executable itself, but rather running this executable under valgrind, and compare the output with expected output). If the test still fails, examine in the memcheck/tests directory the files addressable* Some files will give the expected stdout and stderr output, and some files will give what has really be produced. See README_DEVELOPPERS for more information (this is a very valuable source of information :). Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Julian S. <js...@ac...> - 2010-08-12 08:51:01
|
make -k check builds all the regtests that it can; if something breaks then it just moves on to the next one. Then to run them you can do > To run one test, you must do something like: > perl tests/vg_regtest memcheck/tests/addressable J |