You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
(8) |
2
(10) |
3
(18) |
4
(14) |
5
(16) |
6
(11) |
7
(10) |
|
8
(7) |
9
(8) |
10
(6) |
11
(6) |
12
(9) |
13
(13) |
14
(8) |
|
15
(3) |
16
(6) |
17
(8) |
18
(7) |
19
(7) |
20
(7) |
21
(5) |
|
22
(6) |
23
(5) |
24
(5) |
25
(5) |
26
(7) |
27
(7) |
28
(7) |
|
29
(15) |
30
(11) |
|
|
|
|
|
|
From: Nicholas N. <nj...@cs...> - 2007-04-12 22:08:32
|
Hi, I'm compiling a list of universities and similar institutions that have used Valgrind for research, eg. building new tools with it. This list is on the Valgrind website: http://www.valgrind.org/info/about.html.I currently have the following institutions in the list: Cambridge MIT UC Berkeley Carnegie Mellon Cornell University of New Mexico Australian National University University of Melbourne TU Muenchen Graz University of Technology If you know of any others, please mail me privately. If you could give a brief description of how Valgrind has been used, that would be helpful. Also, if you've written a paper that involved Valgrind and would like it mentioned on http://www.valgrind.org/docs/pubs.html, please email me a copy privately with the relevant details. Thanks, Nick |
|
From: <sv...@va...> - 2007-04-12 21:56:48
|
Author: njn Date: 2007-04-12 22:56:45 +0100 (Thu, 12 Apr 2007) New Revision: 332 Log: tweak Modified: trunk/info/about.html Modified: trunk/info/about.html =================================================================== --- trunk/info/about.html 2007-04-05 04:14:27 UTC (rev 331) +++ trunk/info/about.html 2007-04-12 21:56:45 UTC (rev 332) @@ -20,21 +20,21 @@ find and eliminate bugs before they become a problem.</li> <li>Valgrind can help you speed up your programs. With Valgrind -tools you can also perform very detailed profiling to help speed -up your programs.</li> +tools you can also perform very detailed profiling to help find +bottlenecks in your programs.</li> <li>Valgrind is free. Free-as-in-speech: you can download it, read the source code, make modifications, and pass them on, all within the limits of the GNU GPL. And free-as-in-beer: we aren't charging for it.</li> -<li>Valgrind runs on x86/Linux, AMD64/Linux and PPC32/Linux, several of -the most popular platforms in use. Valgrind works with all the major -Linux distributions, including Red Hat, SuSE, Debian, Gentoo, Slackware, +<li>Valgrind runs on several popular platforms, such as x86/Linux, +AMD64/Linux and PPC32/Linux. Valgrind works with all the major Linux +distributions, including Red Hat, SuSE, Debian, Gentoo, Slackware, Mandrake, etc.</li> <li>Valgrind is easy to use. Valgrind uses dynamic binary -translation, so you don't need to modify, recompile or relink +instrumentation, so you don't need to modify, recompile or relink your applications. Just prefix your command line with valgrind and everything works.</li> @@ -46,25 +46,24 @@ programmers. <li>Valgrind is suitable for any type of software. Valgrind has -been used on almost every kind of software imaginable: desktop -applications, libraries, databases, games, web browsers, network -servers, distributed control systems, virtual reality frameworks, -transaction servers, compilers, interpreters, virtual machines, -telecom applications, embedded software, medical imaging, -scientific programming, signal processing, video/audio programs, -NASA Mars lander vision and rover navigation systems, business -intelligence software, financial/banking software, operating -system daemons, etc, etc. See a list of -<a href="/gallery/users.html">projects using Valgrind</a>.</li> +been used with desktop applications, libraries, databases, games, web +browsers, network servers, distributed control systems, virtual reality +frameworks, transaction servers, compilers, interpreters, virtual +machines, telecom applications, embedded software, medical imaging, +scientific programs, signal processing programs, video/audio programs, +business intelligence software, financial/banking software, operating +system daemons, etc, etc. See a list of <a +href="/gallery/users.html">projects using Valgrind</a>.</li> <li>Valgrind is widely used. Valgrind has been used by thousands of programmers across the world. We have received feedback from -users in over 30 countries, including: Belgium, Czech Republic, +users in over 30 countries.</li> +<!-- Denmark, Finland, France, Germany, Greece, Hungary, Iceland, Italy, The -Netherlands, Norway, Poland, Portugal, Russia, Slovenia, -Sweden, Switzerland, UK, -Argentina, Brazil, Canada, USA, Australia, China, India, Japan, New Zealand, -Singapore, South Africa, Israel and Turkey.</li> +Netherlands, Norway, Poland, Portugal, Russia, Slovenia, Sweden, +Switzerland, UK, Argentina, Brazil, Canada, USA, Australia, China, +India, Japan, New Zealand, Singapore, South Africa, Israel and Turkey. +--> <li>Valgrind works with programs written in any language. Because Valgrind works directly with program binaries, it works with @@ -77,26 +76,19 @@ written partly or entirely in C, C++, Java, Perl, Python, assembly code, Fortran, Ada, and many others.</li> -<li>Valgrind debugs and profiles your entire program. Unlike -tools that require a recompilation step, Valgrind gives you total -debugging and profiling coverage of every instruction executed by -your program, even within system libraries. You can even use -Valgrind on programs for which you don't have the source -code.</li> +<li>Valgrind gives 100% coverage of user-space code, even within system +libraries. You can even use Valgrind on programs for which you don't +have the source code.</li> -<li>Valgrind can be used with other tools. Valgrind can start GDB -and attach it to your program at the point(s) where errors are -detected, so that you can poke around and figure out what was -going on at the time.</li> - -<li>Valgrind is extensible. Valgrind consists of the Valgrind -core, which provides a synthetic software CPU, and Valgrind -tools, which plug into the core, and instrument and analyse the -running program. Anyone can write powerful new tools that add -arbitrary instrumentation to programs. This is much easier than +<li>Valgrind is extensible. Anyone can write powerful new tools that +add arbitrary instrumentation to programs. This is much easier than writing such tools from scratch. This makes Valgrind ideal for -experimenting with new kinds of debuggers, profilers, and similar -tools.</li> +experimenting with new kinds of program analysis tools. +It has been used for research purposes by people at the following +universities: Cambridge, MIT, Berkeley, Carnegie Mellon, Cornell, +University of New Mexico, Australian National University, University of +Melbourne, TU Muenchen (Munich) and Graz University of Technology. +</li> <li>Valgrind is actively maintained. The Valgrind developers are constantly working to fix bugs, improve Valgrind, and ensure it @@ -117,7 +109,7 @@ <h2>When should you use Valgrind?</h2> <p>It depends on your exact needs. Here are some examples of when -people use Valgrind's error-finding tools.</p> +people use Valgrind's bug-detecting tools.</p> <ul> |
|
From: <js...@ac...> - 2007-04-12 12:10:26
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2007-04-12 09:00:02 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 219 tests, 10 stderr failures, 6 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) |
|
From: Kumar R. <kum...@gm...> - 2007-04-12 10:41:23
|
Hi Gurus, A while back someone has posted a note asking if anyone is interested in porting Valgrind to Solaris/x86. Since my company focuses on porting and migration (S7 Solutions), we had offered to do this, but since we are a small company, offered to do it at a charge. Unfortunately the customer's expecation of the expenses toward the porting effort and our estimation did not match, and so we could not pursue further. But I am personally interested in making this happen and am asking my company to even pitch in formally with this effort (ie share the expense). While they have agreed to share the expense, the way we have estimated the effort involved, my company cannot bare the expense fully. We estimated (maybe wrongly, so please correct me) that it would take 3-4 people working full-time, about a year and half to understand Valgrind and make it available on a new platform. This was ofcourse with the intention of doing it like a corporate project with dedicated testing effort and support. This was estimated with our experience in doing similar porting efforts of similar products in my earlier jobs. So my question is, would anyone else be interested to pitch in and fund this project, so that dedicated resources can be put in to make this port a reality ? Or maybe I should be posting it in the users group to check about this ? Thanks, :-) - The problem with winning the rat race is that, even if u win, u r still a rat! |
|
From: Tom H. <th...@cy...> - 2007-04-12 02:32:07
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-04-12 03:15:03 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 256 tests, 27 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/long_namespace_xml (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/x86/xor-undef-x86 (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2007-04-12 02:23:52
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2007-04-12 03:10:09 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 292 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 292 tests, 4 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Apr 12 03:17:04 2007 --- new.short Thu Apr 12 03:23:44 2007 *************** *** 8,10 **** ! == 292 tests, 4 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) --- 8,10 ---- ! == 292 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) *************** *** 14,16 **** none/tests/mremap2 (stdout) - none/tests/pth_detached (stdout) --- 14,15 ---- |
|
From: Tom H. <th...@cy...> - 2007-04-12 02:14:45
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-04-12 03:00:03 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo gcc -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -o nibz_bennee_mmap nibz_bennee_mmap.o if gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -MT slahf-amd64.o -MD -MP -MF ".deps/slahf-amd64.Tpo" -c -o slahf-amd64.o slahf-amd64.c; \ then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi /tmp/ccGWyyZ4.s: Assembler messages: /tmp/ccGWyyZ4.s:27: Error: suffix or operands invalid for `lahf' /tmp/ccGWyyZ4.s:37: Error: suffix or operands invalid for `lahf' /tmp/ccGWyyZ4.s:43: Error: suffix or operands invalid for `sahf' /tmp/ccGWyyZ4.s:45: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 rm insn_sse3.c insn_sse.c insn_mmx.c insn_fpu.c insn_sse2.c insn_basic.c make[5]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind' make: *** [check] Error 2 ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo gcc -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -o nibz_bennee_mmap nibz_bennee_mmap.o if gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -MT slahf-amd64.o -MD -MP -MF ".deps/slahf-amd64.Tpo" -c -o slahf-amd64.o slahf-amd64.c; \ then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi /tmp/ccu90h1D.s: Assembler messages: /tmp/ccu90h1D.s:27: Error: suffix or operands invalid for `lahf' /tmp/ccu90h1D.s:37: Error: suffix or operands invalid for `lahf' /tmp/ccu90h1D.s:43: Error: suffix or operands invalid for `sahf' /tmp/ccu90h1D.s:45: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 rm insn_sse3.c insn_sse.c insn_mmx.c insn_fpu.c insn_sse2.c insn_basic.c make[5]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Apr 12 03:07:28 2007 --- new.short Thu Apr 12 03:14:39 2007 *************** *** 10,16 **** then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi ! /tmp/ccu90h1D.s: Assembler messages: ! /tmp/ccu90h1D.s:27: Error: suffix or operands invalid for `lahf' ! /tmp/ccu90h1D.s:37: Error: suffix or operands invalid for `lahf' ! /tmp/ccu90h1D.s:43: Error: suffix or operands invalid for `sahf' ! /tmp/ccu90h1D.s:45: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 --- 10,16 ---- then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi ! /tmp/ccGWyyZ4.s: Assembler messages: ! /tmp/ccGWyyZ4.s:27: Error: suffix or operands invalid for `lahf' ! /tmp/ccGWyyZ4.s:37: Error: suffix or operands invalid for `lahf' ! /tmp/ccGWyyZ4.s:43: Error: suffix or operands invalid for `sahf' ! /tmp/ccGWyyZ4.s:45: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2007-04-12 02:12:42
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2007-04-12 03:05:08 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo gcc -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -o nibz_bennee_mmap nibz_bennee_mmap.o if gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -MT slahf-amd64.o -MD -MP -MF ".deps/slahf-amd64.Tpo" -c -o slahf-amd64.o slahf-amd64.c; \ then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi /tmp/cc8ubSlj.s: Assembler messages: /tmp/cc8ubSlj.s:18: Error: suffix or operands invalid for `lahf' /tmp/cc8ubSlj.s:28: Error: suffix or operands invalid for `lahf' /tmp/cc8ubSlj.s:34: Error: suffix or operands invalid for `sahf' /tmp/cc8ubSlj.s:36: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 rm insn_sse3.c insn_sse.c insn_mmx.c insn_fpu.c insn_sse2.c insn_basic.c make[5]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind' make: *** [check] Error 2 ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo gcc -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -o nibz_bennee_mmap nibz_bennee_mmap.o if gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wdeclaration-after-statement -MT slahf-amd64.o -MD -MP -MF ".deps/slahf-amd64.Tpo" -c -o slahf-amd64.o slahf-amd64.c; \ then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi /tmp/ccTLig9j.s: Assembler messages: /tmp/ccTLig9j.s:18: Error: suffix or operands invalid for `lahf' /tmp/ccTLig9j.s:28: Error: suffix or operands invalid for `lahf' /tmp/ccTLig9j.s:34: Error: suffix or operands invalid for `sahf' /tmp/ccTLig9j.s:36: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 rm insn_sse3.c insn_sse.c insn_mmx.c insn_fpu.c insn_sse2.c insn_basic.c make[5]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests/amd64' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2007-04-12/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Apr 12 03:09:41 2007 --- new.short Thu Apr 12 03:12:34 2007 *************** *** 10,16 **** then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi ! /tmp/ccTLig9j.s: Assembler messages: ! /tmp/ccTLig9j.s:18: Error: suffix or operands invalid for `lahf' ! /tmp/ccTLig9j.s:28: Error: suffix or operands invalid for `lahf' ! /tmp/ccTLig9j.s:34: Error: suffix or operands invalid for `sahf' ! /tmp/ccTLig9j.s:36: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 --- 10,16 ---- then mv -f ".deps/slahf-amd64.Tpo" ".deps/slahf-amd64.Po"; else rm -f ".deps/slahf-amd64.Tpo"; exit 1; fi ! /tmp/cc8ubSlj.s: Assembler messages: ! /tmp/cc8ubSlj.s:18: Error: suffix or operands invalid for `lahf' ! /tmp/cc8ubSlj.s:28: Error: suffix or operands invalid for `lahf' ! /tmp/cc8ubSlj.s:34: Error: suffix or operands invalid for `sahf' ! /tmp/cc8ubSlj.s:36: Error: suffix or operands invalid for `lahf' make[5]: *** [slahf-amd64.o] Error 1 |
|
From: <js...@ac...> - 2007-04-12 00:16:41
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-04-12 02:00:01 CEST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 226 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |