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
(32) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
(39) |
2
(29) |
3
(27) |
4
(50) |
5
(37) |
|
6
(14) |
7
(28) |
8
(44) |
9
(38) |
10
(32) |
11
(49) |
12
(51) |
|
13
(37) |
14
(32) |
15
(70) |
16
(50) |
17
(43) |
18
(56) |
19
(23) |
|
20
(22) |
21
(36) |
22
(12) |
23
(22) |
24
(10) |
25
(13) |
26
(21) |
|
27
(17) |
28
(16) |
29
(33) |
30
(14) |
|
|
|
|
From: Tom H. <to...@co...> - 2005-11-15 11:07:36
|
In message <200...@cn...>
Yao Qi <qiy...@cn...> wrote:
> The part about debugging Valgrind in README_DEVELOPERS is out-of-date.
> I code a patch for this.
I actually think we should drop all that - there are much easier ways
to debug valgrind now that everything is statically linked with the
tool:
- Set VALGRIND_LAUNCHER to <prefix>/bin/valgrind
- Run "gdb <prefix>/lib/valgrind/<platform>/<tool>"
- Do "handle SIGSEGV nostop noprint" to stop gdb stopping on
a SEGV as valgrindd needs to be able to handle them to do
stack extension
- Set any breakpoints you want and proceed as normal for gdb
In principle debugging valgrind itself should work, the only problem
is getting control when it starts the tool to set breakpoints. Doing
a "catch exec" doesn't really work as that stops before the exec and
my gdb doesn't implement "catch start" or "catch thread_start".
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Tom H. <to...@co...> - 2005-11-15 10:48:08
|
In message <200...@gm...>
Josef Weidendorfer <Jos...@gm...> wrote:
> I plan to release Callgrind both for VG 3.0 and VG 3.1 as one package.
> These means that I have two similar, but different build targets
> which are conditionally built dependent on the Valgrind installation
> found: for VG 3.0, I build a shared library, for VG 3.1 a static linked
> binary.
>
> Currently, I try to use two different subdirs/Makefile.am's for this,
> using in the toplevel Makefile.am
>
> SUBDIRS = $(CG_SRCDIR)
>
> CG_SRCDIR is set to the right build directory dependent on what
> configure detected.
Sounds horrid, but still... Sounds like I'm going to have fun getting
my in tree builds to work ;-)
> The problem is that "make dist" only includes one of the build dirs,
> not both.
Indeed - it will only include the one you've configured for.
The solution is to set DIST_SUBDIRS to list both directories.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: <sv...@va...> - 2005-11-15 10:28:07
|
Author: sewardj Date: 2005-11-15 10:27:41 +0000 (Tue, 15 Nov 2005) New Revision: 229 Log: put direct changes to /usr/local/www/sites/valgrind-www into repo Modified: trunk/.htaccess trunk/robots.txt Modified: trunk/.htaccess =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/.htaccess 2005-11-14 21:17:04 UTC (rev 228) +++ trunk/.htaccess 2005-11-15 10:27:41 UTC (rev 229) @@ -11,9 +11,9 @@ =20 # set the include path: # this is for phoenix: -php_value include_path "/home/de/WebPages/valgrind-www/trunk/php" +# php_value include_path "/home/de/WebPages/valgrind-www/trunk/php" # this is for exonetric: -# php_value include_path "/usr/local/www/sites/valgrind-www/php" +php_value include_path "/usr/local/www/sites/valgrind-www/php" =20 =20 # prepend these files to every .html file: Modified: trunk/robots.txt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/robots.txt 2005-11-14 21:17:04 UTC (rev 228) +++ trunk/robots.txt 2005-11-15 10:27:41 UTC (rev 229) @@ -13,6 +13,9 @@ User-agent: * Disallow: /errors =20 +User-agent: * +Disallow: /stats.htm + # change this later when the bookset comes online User-agent: * Disallow: /docs/bookset |
|
From: <sv...@va...> - 2005-11-15 10:21:22
|
Author: sewardj
Date: 2005-11-15 10:21:19 +0000 (Tue, 15 Nov 2005)
New Revision: 1459
Log:
delete unused multiply primops
Modified:
trunk/priv/ir/irdefs.c
trunk/pub/libvex_ir.h
Modified: trunk/priv/ir/irdefs.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/priv/ir/irdefs.c 2005-11-14 03:32:23 UTC (rev 1458)
+++ trunk/priv/ir/irdefs.c 2005-11-15 10:21:19 UTC (rev 1459)
@@ -437,10 +437,6 @@
case Iop_QSub32Sx4: vex_printf("QSub32Sx4"); return;
=20
case Iop_Mul16x8: vex_printf("Mul16x8"); return;
- case Iop_MulLo16Ux8: vex_printf("MulLo16Ux8"); return;
- case Iop_MulLo32Ux4: vex_printf("MulLo32Ux4"); return;
- case Iop_MulLo16Sx8: vex_printf("MulLo16Sx8"); return;
- case Iop_MulLo32Sx4: vex_printf("MulLo32Sx4"); return;
case Iop_MulHi16Ux8: vex_printf("MulHi16Ux8"); return;
case Iop_MulHi32Ux4: vex_printf("MulHi32Ux4"); return;
case Iop_MulHi16Sx8: vex_printf("MulHi16Sx8"); return;
@@ -1560,8 +1556,6 @@
case Iop_QSub8Ux16: case Iop_QSub16Ux8: case Iop_QSub32Ux4:
case Iop_QSub8Sx16: case Iop_QSub16Sx8: case Iop_QSub32Sx4:
case Iop_Mul16x8:
- case Iop_MulLo16Ux8: case Iop_MulLo32Ux4:
- case Iop_MulLo16Sx8: case Iop_MulLo32Sx4:
case Iop_MulHi16Ux8: case Iop_MulHi32Ux4:=20
case Iop_MulHi16Sx8: case Iop_MulHi32Sx4:=20
case Iop_MullEven8Ux16: case Iop_MullEven16Ux8:
Modified: trunk/pub/libvex_ir.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/pub/libvex_ir.h 2005-11-14 03:32:23 UTC (rev 1458)
+++ trunk/pub/libvex_ir.h 2005-11-15 10:21:19 UTC (rev 1459)
@@ -550,8 +550,6 @@
=20
/* MULTIPLICATION (normal / high half of signed/unsigned) */
Iop_Mul16x8,
- Iop_MulLo16Ux8, Iop_MulLo32Ux4,
- Iop_MulLo16Sx8, Iop_MulLo32Sx4,
Iop_MulHi16Ux8, Iop_MulHi32Ux4,
Iop_MulHi16Sx8, Iop_MulHi32Sx4,
/* (widening signed/unsigned of even lanes, with lowest lane=3Dzer=
o) */
|
|
From: Josef W. <Jos...@gm...> - 2005-11-15 09:46:17
|
Hi, I plan to release Callgrind both for VG 3.0 and VG 3.1 as one package. These means that I have two similar, but different build targets which are conditionally built dependent on the Valgrind installation found: for VG 3.0, I build a shared library, for VG 3.1 a static linked binary. Currently, I try to use two different subdirs/Makefile.am's for this, using in the toplevel Makefile.am SUBDIRS = $(CG_SRCDIR) CG_SRCDIR is set to the right build directory dependent on what configure detected. The problem is that "make dist" only includes one of the build dirs, not both. Ideas? Thanks, Josef |
|
From: Josef W. <Jos...@gm...> - 2005-11-15 09:39:56
|
Hi,
I have a better working callgrind for PPC now ...
Two issues:
1) There is a "strange function" with a single instruction "blrl".
It is called quite often at the start of any code in /lib/ld.so,
address 0x04027528; ld.so is mapped starting from 0x04000000.
According to objdump, 27528 is still part of ld.so:
objdump -d /lib/ld-2.3.5.so | less
Disassembly of section .got:
00027000 <.got>:
...
27528: 4e 80 00 21 blrl
2752c: 00 02 6f 50 .long 0x26f50
...
So this is code in the GOT table. Thus, the code seems to put the
GOT of a DSO into lr, which then often is put into an general
purpose register (e.g. with mflr r30).
According to callgrind debug output, address 0x04027528 is not attributed
to any segment by valgrind (using VG_(find_seginfo)()).
Looking at proc/XXX/maps, I get:
04000000-04017000 r-xp 00000000 03:03 557124 /lib/ld-2.3.5.so
04017000-0401c000 rw-p 04017000 00:00 0
04026000-04027000 r--p 00016000 03:03 557124 /lib/ld-2.3.5.so
04027000-04028000 rwxp 00017000 03:03 557124 /lib/ld-2.3.5.so
Does anybody have an idea what can cause this?
I use the segment info to decide if a boring jump should be changed
to a call (ie. when crossing segment boundaries; this is for x86/x86_64
from PLT section to another DSO).
Josef
|
|
From: Yao Qi <qiy...@cn...> - 2005-11-15 07:09:31
|
The part about debugging Valgrind in README_DEVELOPERS is out-of-date. I code a patch for this. =================================================================== --- README_DEVELOPERS (revision 5114) +++ README_DEVELOPERS (working copy) @@ -37,20 +37,30 @@ ~~~~~~~~~~~~~~~~~~~~~~~~~~~ To debug stage 1 just run it under GDB in the normal way. -To debug Valgrind proper (stage 2) with GDB, start Valgrind like this: +To debug Valgrind proper tool, none for example, with GDB, start +Valgrind like this: valgrind --tool=none --wait-for-gdb=yes <prog> -Then start gdb like this in another terminal: +Then start GDB like this in another terminal: - gdb /usr/lib/valgrind/stage2 <pid> + gdb /usr/local/lib/valgrind/lib/<platform>/none <pid> -Where <pid> is the pid valgrind printed. Then set whatever breakpoints -you want and do this in gdb: +If you want to debug Valgrind tool without installing it, and you +could start GDB also in another terminal like this: - jump *$eip + gdb ~/grind/head4/.in_place/<platform>/none <pid> +Where <platform> is the current platform Valgrind build on and <pid> +is the pid Valgrind printed. +Then set whatever breakpoints you want and do this in GDB: + + jump *$eip (on X86 or AMD64) +or, + jump *$pc (on PPC32) + + Self-hosting ~~~~~~~~~~~~ To run Valgrind under Valgrind: -- Regards, Yao ------------ Yao Qi |
|
From: Yao Qi <qiy...@cn...> - 2005-11-15 06:55:00
|
On Mon, Nov 14, 2005 at 12:44:10PM +0000, Julian Seward wrote:
>
> > - fix none/tests/ppc32/jm-insns.c so it works with gcc4.
>
> It compiles OK with gcc4, but segfaults due for no obvious reason.
> I think it is due somehow to the use of global register variables
> in an unsafe way (basically the program is clever but the implementation
> is unsafe).
I run jm-insns compiled by GCC-4.1.0, and this is the output,
[qiyao@linux valgrind]$
VALGRIND_LIB=/home/qiyao/svn/valgrind/.in_place ./coregrind/valgrind
--tool=none none/tests/ppc32/jm-insns
PPC integer compare with immediate insns (two args):
copy func cmpi from 0x10000ec0 to 0xfeffe454 (9421fff0 93e1000c)
=> func cmpi from 0xfeffe454 to 0xfeffe454 (94210000 93e1000c)
disInstr(ppc32): unhandled instruction: 0x0
primary 0(0x0), secondary 0(0x0)
==10717== Your program just tried to execute an
instruction that Valgrind
==10717== did not recognise. There are two possible
reasons for this.
==10717== 1. Your program has a bug and erroneously
jumped to a non-code
==10717== location. If you are running Memcheck
and you just saw a
==10717== warning about a bad jump, it's probably
your program's fault.
==10717== 2. The instruction is legitimate but
Valgrind doesn't handle it,
==10717== i.e. it's Valgrind's fault. If you think
this is the case or
==10717== you are not sure, please let us know.
==10717== Either way, Valgrind will now raise a SIGILL
signal which will
==10717== probably kill your program.
==10717==
==10717== Process terminating with default action of
signal 4 (SIGILL)
==10717== Illegal opcode at address 0xFEFFE45C
==10717== at 0xFEFFE45C: ???
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717==
Illegal instruction
Do you mean this is a "segfault"? I am not sure whether I am on a
right track.
>
> > Maybe I could code patch on this to move all the declarations in front
> > of statements to remove all the compiler warnings, any thought on this?
>
> That would be good. Even better if you can fix it to remove the
> segfaults.
It seem that code in test_int_one_reg_imm16 makes some trouble for me,
3938 func_buf[1] = p[1];
3939 patch_op_imm16(func_buf, p, ii16[j]);
3940 func = (void *)func_buf;
......
......
3955 (*func)();
This program received a signal SIGILL(Illegal instruction) when it
executed at line 3955. I am not sure of the purpose of this slice of
code, I guess these are done on purpose, but I can't make out exactly.
This test works util I remove all the tests about immediate args from
all_tests[]. Would any one have a look? Any suggestions are highly
appreciated!
>
> J
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>
--
Regards, Yao
------------
Yao Qi
|
|
From: Yao Qi <qiy...@cn...> - 2005-11-15 06:49:42
|
On Mon, Nov 14, 2005 at 12:44:10PM +0000, Julian Seward wrote:
>
> > - fix none/tests/ppc32/jm-insns.c so it works with gcc4.
>
> It compiles OK with gcc4, but segfaults due for no obvious reason.
> I think it is due somehow to the use of global register variables
> in an unsafe way (basically the program is clever but the implementation
> is unsafe).
I run jm-insns compiled by GCC-4.1.0, and this is the output,
[qiyao@linux valgrind]$
VALGRIND_LIB=/home/qiyao/svn/valgrind/.in_place ./coregrind/valgrind
--tool=none none/tests/ppc32/jm-insns
PPC integer compare with immediate insns (two args):
copy func cmpi from 0x10000ec0 to 0xfeffe454 (9421fff0 93e1000c)
=> func cmpi from 0xfeffe454 to 0xfeffe454 (94210000 93e1000c)
disInstr(ppc32): unhandled instruction: 0x0
primary 0(0x0), secondary 0(0x0)
==10717== Your program just tried to execute an
instruction that Valgrind
==10717== did not recognise. There are two possible
reasons for this.
==10717== 1. Your program has a bug and erroneously
jumped to a non-code
==10717== location. If you are running Memcheck
and you just saw a
==10717== warning about a bad jump, it's probably
your program's fault.
==10717== 2. The instruction is legitimate but
Valgrind doesn't handle it,
==10717== i.e. it's Valgrind's fault. If you think
this is the case or
==10717== you are not sure, please let us know.
==10717== Either way, Valgrind will now raise a SIGILL
signal which will
==10717== probably kill your program.
==10717==
==10717== Process terminating with default action of
signal 4 (SIGILL)
==10717== Illegal opcode at address 0xFEFFE45C
==10717== at 0xFEFFE45C: ???
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717== by 0x10003440: test_int_one_reg_imm16
(jm-insns.c:3942)
==10717==
Illegal instruction
Do you mean this is a "segfault"? I am not sure whether I am on a
right track.
>
> > Maybe I could code patch on this to move all the declarations in front
> > of statements to remove all the compiler warnings, any thought on this?
>
> That would be good. Even better if you can fix it to remove the
> segfaults.
It seem that code in test_int_one_reg_imm16 makes some trouble for me,
3938 func_buf[1] = p[1];
3939 patch_op_imm16(func_buf, p, ii16[j]);
3940 func = (void *)func_buf;
......
......
3955 (*func)();
This program received a signal SIGILL(Illegal instruction) when it
executed at line 3955. I am not sure of the purpose of this slice of
code, I guess these are done on purpose, but I can't make out exactly.
This test works util I remove all the tests about immediate args from
all_tests[]. Would any one have a look? Any suggestions are highly
appreciated!
>
> J
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>
--
Regards, Yao
------------
Yao Qi
|
|
From: <js...@ac...> - 2005-11-15 03:51:36
|
Nightly build on phoenix ( SuSE 9.1 ) started at 2005-11-15 03:30:01 GMT
Checking out vex source tree ... done
Building vex ... done
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 209 tests, 91 stderr failures, 2 stdout failures =================
memcheck/tests/addressable (stderr)
memcheck/tests/badaddrvalue (stderr)
memcheck/tests/badfree (stderr)
memcheck/tests/badjump (stderr)
memcheck/tests/badjump2 (stderr)
memcheck/tests/badloop (stderr)
memcheck/tests/badpoll (stderr)
memcheck/tests/badrw (stderr)
memcheck/tests/brk (stderr)
memcheck/tests/brk2 (stderr)
memcheck/tests/buflen_check (stderr)
memcheck/tests/clientperm (stderr)
memcheck/tests/custom_alloc (stderr)
memcheck/tests/describe-block (stderr)
memcheck/tests/doublefree (stderr)
memcheck/tests/erringfds (stderr)
memcheck/tests/error_counts (stdout)
memcheck/tests/errs1 (stderr)
memcheck/tests/execve (stderr)
memcheck/tests/execve2 (stderr)
memcheck/tests/exitprog (stderr)
memcheck/tests/fprw (stderr)
memcheck/tests/fwrite (stderr)
memcheck/tests/inits (stderr)
memcheck/tests/inline (stderr)
memcheck/tests/leak-0 (stderr)
memcheck/tests/leak-cycle (stderr)
memcheck/tests/leak-regroot (stderr)
memcheck/tests/leak-tree (stderr)
memcheck/tests/malloc1 (stderr)
memcheck/tests/malloc2 (stderr)
memcheck/tests/malloc3 (stderr)
memcheck/tests/malloc_usable (stderr)
memcheck/tests/manuel1 (stderr)
memcheck/tests/manuel2 (stderr)
memcheck/tests/manuel3 (stderr)
memcheck/tests/match-overrun (stderr)
memcheck/tests/memalign2 (stderr)
memcheck/tests/memalign_test (stderr)
memcheck/tests/memcmptest (stderr)
memcheck/tests/mempool (stderr)
memcheck/tests/mismatches (stderr)
memcheck/tests/mmaptest (stderr)
memcheck/tests/nanoleak (stderr)
memcheck/tests/nanoleak_supp (stderr)
memcheck/tests/new_nothrow (stderr)
memcheck/tests/new_override (stderr)
memcheck/tests/null_socket (stderr)
memcheck/tests/oset_test (stderr)
memcheck/tests/overlap (stderr)
memcheck/tests/partial_load_dflt (stderr)
memcheck/tests/partial_load_ok (stderr)
memcheck/tests/partiallydefinedeq (stderr)
memcheck/tests/pipe (stderr)
memcheck/tests/pointer-trace (stderr)
memcheck/tests/post-syscall (stderr)
memcheck/tests/realloc1 (stderr)
memcheck/tests/realloc2 (stderr)
memcheck/tests/realloc3 (stderr)
memcheck/tests/sigaltstack (stderr)
memcheck/tests/sigkill (stderr)
memcheck/tests/signal2 (stderr)
memcheck/tests/sigprocmask (stderr)
memcheck/tests/stack_changes (stderr)
memcheck/tests/stack_switch (stderr)
memcheck/tests/str_tester (stderr)
memcheck/tests/strchr (stderr)
memcheck/tests/supp1 (stderr)
memcheck/tests/supp2 (stderr)
memcheck/tests/supp_unknown (stderr)
memcheck/tests/suppfree (stderr)
memcheck/tests/toobig-allocs (stderr)
memcheck/tests/trivialleak (stderr)
memcheck/tests/with-space (stderr)
memcheck/tests/writev (stderr)
memcheck/tests/x86/fpeflags (stderr)
memcheck/tests/x86/insn_basic (stderr)
memcheck/tests/x86/insn_cmov (stderr)
memcheck/tests/x86/insn_fpu (stderr)
memcheck/tests/x86/insn_mmx (stderr)
memcheck/tests/x86/insn_sse (stderr)
memcheck/tests/x86/pushfpopf (stderr)
memcheck/tests/x86/scalar (stderr)
memcheck/tests/x86/scalar_exit_group (stderr)
memcheck/tests/x86/scalar_fork (stderr)
memcheck/tests/x86/scalar_supp (stderr)
memcheck/tests/x86/scalar_vfork (stderr)
memcheck/tests/x86/tronical (stderr)
memcheck/tests/xml1 (stderr)
memcheck/tests/zeropage (stderr)
none/tests/mremap2 (stdout)
none/tests/x86/faultstatus (stderr)
none/tests/x86/int (stderr)
=================================================
== Results from 24 hours ago ==
=================================================
Checking out vex source tree ... done
Building vex ... failed
Last 20 lines of verbose log follow echo
-c priv/ir/irmatch.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/ir/iropt.o \
-c priv/ir/iropt.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/main/vex_main.o \
-c priv/main/vex_main.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/main/vex_globals.o \
-c priv/main/vex_globals.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/main/vex_util.o \
-c priv/main/vex_util.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-x86/hdefs.o \
-c priv/host-x86/hdefs.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-amd64/hdefs.o \
-c priv/host-amd64/hdefs.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-arm/hdefs.o \
-c priv/host-arm/hdefs.c
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-ppc32/hdefs.o \
-c priv/host-ppc32/hdefs.c
priv/host-ppc32/hdefs.c:696: error: conflicting types for 'showPPC32AvFpOp'
priv/host-ppc32/hdefs.h:420: error: previous declaration of 'showPPC32AvFpOp' was here
make: *** [priv/host-ppc32/hdefs.o] Error 1
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Tue Nov 15 03:31:06 2005
--- new.short Tue Nov 15 03:51:38 2005
***************
*** 2,25 ****
Checking out vex source tree ... done
! Building vex ... failed
- Last 20 lines of verbose log follow echo
- -c priv/ir/irmatch.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/ir/iropt.o \
- -c priv/ir/iropt.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/main/vex_main.o \
- -c priv/main/vex_main.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/main/vex_globals.o \
- -c priv/main/vex_globals.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/main/vex_util.o \
- -c priv/main/vex_util.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-x86/hdefs.o \
- -c priv/host-x86/hdefs.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-amd64/hdefs.o \
- -c priv/host-amd64/hdefs.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-arm/hdefs.o \
- -c priv/host-arm/hdefs.c
- gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub -Ipriv -o priv/host-ppc32/hdefs.o \
- -c priv/host-ppc32/hdefs.c
- priv/host-ppc32/hdefs.c:696: error: conflicting types for 'showPPC32AvFpOp'
- priv/host-ppc32/hdefs.h:420: error: previous declaration of 'showPPC32AvFpOp' was here
- make: *** [priv/host-ppc32/hdefs.o] Error 1
--- 2,105 ----
Checking out vex source tree ... done
! Building vex ... done
! Checking out valgrind source tree ... done
! Configuring valgrind ... done
! Building valgrind ... done
! Running regression tests ... failed
!
! Regression test results follow
!
! == 209 tests, 91 stderr failures, 2 stdout failures =================
! memcheck/tests/addressable (stderr)
! memcheck/tests/badaddrvalue (stderr)
! memcheck/tests/badfree (stderr)
! memcheck/tests/badjump (stderr)
! memcheck/tests/badjump2 (stderr)
! memcheck/tests/badloop (stderr)
! memcheck/tests/badpoll (stderr)
! memcheck/tests/badrw (stderr)
! memcheck/tests/brk (stderr)
! memcheck/tests/brk2 (stderr)
! memcheck/tests/buflen_check (stderr)
! memcheck/tests/clientperm (stderr)
! memcheck/tests/custom_alloc (stderr)
! memcheck/tests/describe-block (stderr)
! memcheck/tests/doublefree (stderr)
! memcheck/tests/erringfds (stderr)
! memcheck/tests/error_counts (stdout)
! memcheck/tests/errs1 (stderr)
! memcheck/tests/execve (stderr)
! memcheck/tests/execve2 (stderr)
! memcheck/tests/exitprog (stderr)
! memcheck/tests/fprw (stderr)
! memcheck/tests/fwrite (stderr)
! memcheck/tests/inits (stderr)
! memcheck/tests/inline (stderr)
! memcheck/tests/leak-0 (stderr)
! memcheck/tests/leak-cycle (stderr)
! memcheck/tests/leak-regroot (stderr)
! memcheck/tests/leak-tree (stderr)
! memcheck/tests/malloc1 (stderr)
! memcheck/tests/malloc2 (stderr)
! memcheck/tests/malloc3 (stderr)
! memcheck/tests/malloc_usable (stderr)
! memcheck/tests/manuel1 (stderr)
! memcheck/tests/manuel2 (stderr)
! memcheck/tests/manuel3 (stderr)
! memcheck/tests/match-overrun (stderr)
! memcheck/tests/memalign2 (stderr)
! memcheck/tests/memalign_test (stderr)
! memcheck/tests/memcmptest (stderr)
! memcheck/tests/mempool (stderr)
! memcheck/tests/mismatches (stderr)
! memcheck/tests/mmaptest (stderr)
! memcheck/tests/nanoleak (stderr)
! memcheck/tests/nanoleak_supp (stderr)
! memcheck/tests/new_nothrow (stderr)
! memcheck/tests/new_override (stderr)
! memcheck/tests/null_socket (stderr)
! memcheck/tests/oset_test (stderr)
! memcheck/tests/overlap (stderr)
! memcheck/tests/partial_load_dflt (stderr)
! memcheck/tests/partial_load_ok (stderr)
! memcheck/tests/partiallydefinedeq (stderr)
! memcheck/tests/pipe (stderr)
! memcheck/tests/pointer-trace (stderr)
! memcheck/tests/post-syscall (stderr)
! memcheck/tests/realloc1 (stderr)
! memcheck/tests/realloc2 (stderr)
! memcheck/tests/realloc3 (stderr)
! memcheck/tests/sigaltstack (stderr)
! memcheck/tests/sigkill (stderr)
! memcheck/tests/signal2 (stderr)
! memcheck/tests/sigprocmask (stderr)
! memcheck/tests/stack_changes (stderr)
! memcheck/tests/stack_switch (stderr)
! memcheck/tests/str_tester (stderr)
! memcheck/tests/strchr (stderr)
! memcheck/tests/supp1 (stderr)
! memcheck/tests/supp2 (stderr)
! memcheck/tests/supp_unknown (stderr)
! memcheck/tests/suppfree (stderr)
! memcheck/tests/toobig-allocs (stderr)
! memcheck/tests/trivialleak (stderr)
! memcheck/tests/with-space (stderr)
! memcheck/tests/writev (stderr)
! memcheck/tests/x86/fpeflags (stderr)
! memcheck/tests/x86/insn_basic (stderr)
! memcheck/tests/x86/insn_cmov (stderr)
! memcheck/tests/x86/insn_fpu (stderr)
! memcheck/tests/x86/insn_mmx (stderr)
! memcheck/tests/x86/insn_sse (stderr)
! memcheck/tests/x86/pushfpopf (stderr)
! memcheck/tests/x86/scalar (stderr)
! memcheck/tests/x86/scalar_exit_group (stderr)
! memcheck/tests/x86/scalar_fork (stderr)
! memcheck/tests/x86/scalar_supp (stderr)
! memcheck/tests/x86/scalar_vfork (stderr)
! memcheck/tests/x86/tronical (stderr)
! memcheck/tests/xml1 (stderr)
! memcheck/tests/zeropage (stderr)
! none/tests/mremap2 (stdout)
! none/tests/x86/faultstatus (stderr)
! none/tests/x86/int (stderr)
|
|
From: <js...@ac...> - 2005-11-15 03:45:08
|
Nightly build on g5 ( YDL 4.0, ppc970 ) started at 2005-11-15 04:40:00 CET Checking out vex source tree ... done Building vex ... done Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 175 tests, 18 stderr failures, 0 stdout failures ================= memcheck/tests/badjump (stderr) memcheck/tests/badjump2 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/supp1 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/toobig-allocs (stderr) memcheck/tests/xml1 (stderr) cachegrind/tests/chdir (stderr) cachegrind/tests/clreq (stderr) cachegrind/tests/dlclose (stderr) massif/tests/toobig-allocs (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/fdleak_ipv4 (stderr) none/tests/mremap (stderr) |
|
From: Tom H. <to...@co...> - 2005-11-15 03:42:39
|
Nightly build on dunsmere ( athlon, Fedora Core 4 ) started at 2005-11-15 03:30:06 GMT 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 == 211 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == 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 == 211 tests, 7 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Nov 15 03:36:19 2005 --- new.short Tue Nov 15 03:42:33 2005 *************** *** 8,12 **** ! == 211 tests, 7 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) - memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) --- 8,11 ---- ! == 211 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) |
|
From: Tom H. <th...@cy...> - 2005-11-15 03:26:19
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2005-11-15 03:15:05 GMT 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 == 210 tests, 17 stderr failures, 2 stdout failures ================= memcheck/tests/addressable (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (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) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) none/tests/x86/yield (stdout) ================================================= == 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 if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../include -I../../coregrind -I../../include -I../../VEX/pub -Winline -Wall -Wshadow -g -Wno-long-long -MT stack_switch.o -MD -MP -MF ".deps/stack_switch.Tpo" \ -c -o stack_switch.o `test -f 'stack_switch.c' || echo './'`stack_switch.c; \ then mv -f ".deps/stack_switch.Tpo" ".deps/stack_switch.Po"; \ else rm -f ".deps/stack_switch.Tpo"; exit 1; \ fi stack_switch.c: In function `main': stack_switch.c:40: `CLONE_THREAD' undeclared (first use in this function) stack_switch.c:40: (Each undeclared identifier is reported only once stack_switch.c:40: for each function it appears in.) make[5]: *** [stack_switch.o] Error 1 make[5]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck/tests' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck/tests' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.3583/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Nov 15 03:18:45 2005 --- new.short Tue Nov 15 03:26:12 2005 *************** *** 6,27 **** ! Last 20 lines of verbose log follow echo ! if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../include -I../../coregrind -I../../include -I../../VEX/pub -Winline -Wall -Wshadow -g -Wno-long-long -MT stack_switch.o -MD -MP -MF ".deps/stack_switch.Tpo" \ ! -c -o stack_switch.o `test -f 'stack_switch.c' || echo './'`stack_switch.c; \ ! then mv -f ".deps/stack_switch.Tpo" ".deps/stack_switch.Po"; \ ! else rm -f ".deps/stack_switch.Tpo"; exit 1; \ ! fi ! stack_switch.c: In function `main': ! stack_switch.c:40: `CLONE_THREAD' undeclared (first use in this function) ! stack_switch.c:40: (Each undeclared identifier is reported only once ! stack_switch.c:40: for each function it appears in.) ! make[5]: *** [stack_switch.o] Error 1 ! make[5]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck/tests' ! make[4]: *** [check-am] Error 2 ! make[4]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck/tests' ! make[3]: *** [check-recursive] Error 1 ! make[3]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck/tests' ! make[2]: *** [check-recursive] Error 1 ! make[2]: Leaving directory `/tmp/valgrind.3583/valgrind/memcheck' ! make[1]: *** [check-recursive] Error 1 ! make[1]: Leaving directory `/tmp/valgrind.3583/valgrind' ! make: *** [check] Error 2 --- 6,29 ---- ! Regression test results follow ! ! == 210 tests, 17 stderr failures, 2 stdout failures ================= ! memcheck/tests/addressable (stderr) ! memcheck/tests/describe-block (stderr) ! memcheck/tests/erringfds (stderr) ! memcheck/tests/leak-0 (stderr) ! memcheck/tests/leak-cycle (stderr) ! memcheck/tests/leak-regroot (stderr) ! memcheck/tests/leak-tree (stderr) ! memcheck/tests/leakotron (stdout) ! memcheck/tests/match-overrun (stderr) ! memcheck/tests/mempool (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) ! none/tests/x86/faultstatus (stderr) ! none/tests/x86/int (stderr) ! none/tests/x86/yield (stdout) ! |
|
From: Tom H. <th...@cy...> - 2005-11-15 03:25:13
|
Nightly build on dellow ( x86_64, Fedora Core 4 ) started at 2005-11-15 03:10:09 GMT 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 == 228 tests, 4 stderr failures, 1 stdout failure ================= memcheck/tests/x86/scalar (stderr) none/tests/amd64/faultstatus (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) |
|
From: Tom H. <th...@cy...> - 2005-11-15 03:22:40
|
Nightly build on aston ( x86_64, Fedora Core 3 ) started at 2005-11-15 03:05:14 GMT 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 == 228 tests, 5 stderr failures, 2 stdout failures ================= memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/amd64/faultstatus (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) none/tests/x86/yield (stdout) |
|
From: Tom H. <th...@cy...> - 2005-11-15 03:19:48
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2005-11-15 03:00:03 GMT 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 == 228 tests, 5 stderr failures, 1 stdout failure ================= memcheck/tests/x86/scalar (stderr) none/tests/amd64/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) none/tests/x86/yield (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 == 228 tests, 5 stderr failures, 1 stdout failure ================= memcheck/tests/x86/scalar (stderr) none/tests/amd64/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/tls (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Nov 15 03:07:19 2005 --- new.short Tue Nov 15 03:19:34 2005 *************** *** 12,16 **** none/tests/fdleak_fcntl (stderr) - none/tests/tls (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) --- 12,16 ---- none/tests/fdleak_fcntl (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) + none/tests/x86/yield (stdout) |
|
From: <sv...@va...> - 2005-11-15 02:24:59
|
Author: njn Date: 2005-11-15 02:24:57 +0000 (Tue, 15 Nov 2005) New Revision: 5132 Log: Remove horribly out-of-date comment. Modified: trunk/memcheck/mc_main.c Modified: trunk/memcheck/mc_main.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/memcheck/mc_main.c 2005-11-14 17:03:54 UTC (rev 5131) +++ trunk/memcheck/mc_main.c 2005-11-15 02:24:57 UTC (rev 5132) @@ -98,29 +98,6 @@ //zz There are actually 4 distinguished secondaries. These are used = to //zz represent a memory range which is either not addressable (validi= ty //zz doesn't matter), addressable+not valid, addressable+valid. -//zz=20 -//zz [...] lots of stuff deleted due to out of date-ness -//zz=20 -//zz As a final optimisation, the alignment and address checks for -//zz 4-byte loads and stores are combined in a neat way. The primary -//zz map is extended to have 262144 entries (2^18), rather than 2^16. -//zz The top 3/4 of these entries are permanently set to the -//zz distinguished secondary map. For a 4-byte load/store, the -//zz top-level map is indexed not with (addr >> 16) but instead f(add= r), -//zz where -//zz=20 -//zz f( XXXX XXXX XXXX XXXX ____ ____ ____ __YZ ) -//zz =3D ____ ____ ____ __YZ XXXX XXXX XXXX XXXX or=20 -//zz =3D ____ ____ ____ __ZY XXXX XXXX XXXX XXXX -//zz=20 -//zz ie the lowest two bits are placed above the 16 high address bits= . -//zz If either of these two bits are nonzero, the address is misalign= ed; -//zz this will select a secondary map from the upper 3/4 of the prima= ry -//zz map. Because this is always the distinguished secondary map, a -//zz (bogus) address check failure will result. The failure handling -//zz code can then figure out whether this is a genuine addr check -//zz failure or whether it is a possibly-legitimate access at a -//zz misaligned address. =20 //zz */ =20 /* --------------- Basic configuration --------------- */ |
|
From: Nicholas N. <nj...@cs...> - 2005-11-15 02:14:36
|
Hi,
For the 3.1.0 release, I propose changing the default --leak-check value
from "summary" to "full".
In the survey (which I'm still processing, slowly), we got these numbers
for how people used this option:
full summary none unspecified
always/almost always 61 0 2 6
sometimes 23 0 1 13
("unspecified" means they said they use "--leak-check" but didn't specify
at what level; that probably means --leak-check=full since
--leak-check=summary is of very little real use.)
This is out of the 179 survey responses. Looks like a pretty overwhelming
usage pattern to me, one worth making the default. I think we could
remove the "summary" option and there would be no complaints.
----
Also, I propose changing the default --num-callers option from 12 to 20.
67 people said they always/almost always use --num-callers, and the values
they use are:
8.. 16 20
20.. 40 22
50..200 13
unspecified 12
Only 2 of those in the 8..16 range were less than 12. I would guess that
those using less than 20 probably don't need it that high because their
stack traces are shorter than 20, as opposed to being longer than 20 but
them only being interested in the top 20. Basically, it's clear that
people like to see the entire stack trace where possible.
Thoughts?
Nick
|
|
From: Nicholas N. <nj...@cs...> - 2005-11-15 01:46:08
|
On Tue, 15 Nov 2005, Julian Seward wrote: > Make friends with the nightly build scripts, and get them going on your > machines. Currently we're testing ppc32 on a 970 running YDL4, but we > also use a Mac Mini running SuSE10 for development. Let us know how > you get on. See nightly/README.txt for some instructions on using the nightly scripts. Nick |
|
From: Julian S. <js...@ac...> - 2005-11-15 01:13:39
|
> On Mon, 14 Nov 2005, dc...@us... wrote: > > I downloaded the valgrind source from the Source Repository on the > > valgrind web site. Can anyone tell me what I have? The heading above > > the svn command indicates that it is 3.0 development line. Is this a > > snapshot of the 3.1.0 development that may lag a couple of weeks behind? > > The bleeding edge of development? > > Bleeding edge. I'll update the page to make it clearer. Yes indeed -- literally up to the nanosecond. As you are subscribed to this list you will also get email notification of any further changes. > > What exactly do I have here? How close is this to the 3.1.0 source that > > is scheduled for release at the end of November? > > Very close. More fixes will go in, but that's the code it will be based > on. I hope that we will be at functionality freeze within the next 24 hours, then it's fixing and bug testing. > > I would like to do some testing of the 3.1.0 product on some of the IBM > > PowerPC machines to determine whether there are significant problems that > > don't show up on your PPC machines. I'd like to do the testing as early > > as possible (as well as after you make the official 3.1.0 release) Good. Start now. > > so > > that hopefully any critical problems can be fixed in time to be pushed > > into the upcoming Linux distributions. > > Great! Yup! > > I assume that the developers may have bug fixes that are in their own > > build areas but not necessarily in the Code Repository. > > Not many, if any. Bug fixes/functionality changes get flushed to the main repo very rapidly. To all intents and purposes, an svn checkout at any moment will give the the same as all the developers have. --- Make friends with the nightly build scripts, and get them going on your machines. Currently we're testing ppc32 on a 970 running YDL4, but we also use a Mac Mini running SuSE10 for development. Let us know how you get on. J |