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
(15) |
2
(17) |
3
(23) |
4
(13) |
5
(7) |
6
(8) |
7
(9) |
|
8
(8) |
9
(31) |
10
(31) |
11
(19) |
12
(11) |
13
(38) |
14
(14) |
|
15
(8) |
16
(11) |
17
(7) |
18
(17) |
19
(12) |
20
(12) |
21
(17) |
|
22
(19) |
23
(33) |
24
(42) |
25
(37) |
26
(23) |
27
(27) |
28
(27) |
|
29
(16) |
30
(52) |
31
(33) |
|
|
|
|
|
From: Tom H. <th...@cy...> - 2004-08-16 19:47:06
|
CVS commit by thughes:
Add support for the parallel port ioctls.
CCMAIL: 864...@bu...
M +125 -0 vg_syscalls.c 1.124
M +1 -0 vg_unsafe.h 1.32
--- valgrind/coregrind/vg_syscalls.c #1.123:1.124
@@ -3424,4 +3424,86 @@ PRE(ioctl)
#endif
+ case PPCLAIM:
+ case PPEXCL:
+ case PPYIELD:
+ case PPRELEASE:
+ break;
+ case PPSETMODE:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPSETMODE)", arg3,
+ sizeof(int) );
+ break;
+ case PPGETMODE:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPGETMODE)", arg3,
+ sizeof(int) );
+ break;
+ case PPSETPHASE:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPSETPHASE)", arg3,
+ sizeof(int) );
+ break;
+ case PPGETPHASE:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPGETPHASE)", arg3,
+ sizeof(int) );
+ break;
+ case PPGETMODES:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPGETMODES)", arg3,
+ sizeof(unsigned int) );
+ break;
+ case PPSETFLAGS:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPSETFLAGS)", arg3,
+ sizeof(int) );
+ break;
+ case PPGETFLAGS:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPGETFLAGS)", arg3,
+ sizeof(int) );
+ break;
+ case PPRSTATUS:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPRSTATUS)", arg3,
+ sizeof(unsigned char) );
+ break;
+ case PPRDATA:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPRDATA)", arg3,
+ sizeof(unsigned char) );
+ break;
+ case PPRCONTROL:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPRCONTROL)", arg3,
+ sizeof(unsigned char) );
+ break;
+ case PPWDATA:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPWDATA)", arg3,
+ sizeof(unsigned char) );
+ break;
+ case PPWCONTROL:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPWCONTROL)", arg3,
+ sizeof(unsigned char) );
+ break;
+ case PPFCONTROL:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPFCONTROL)", arg3,
+ 2 * sizeof(unsigned char) );
+ break;
+ case PPDATADIR:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPDATADIR)", arg3,
+ sizeof(int) );
+ break;
+ case PPNEGOT:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPNEGOT)", arg3,
+ sizeof(int) );
+ break;
+ case PPWCTLONIRQ:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPWCTLONIRQ)", arg3,
+ sizeof(unsigned char) );
+ break;
+ case PPCLRIRQ:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPCLRIRQ)", arg3,
+ sizeof(int) );
+ break;
+ case PPSETTIME:
+ SYSCALL_TRACK( pre_mem_read, tid, "ioctl(PPSETTIME)", arg3,
+ sizeof(struct timeval) );
+ break;
+ case PPGETTIME:
+ SYSCALL_TRACK( pre_mem_write, tid, "ioctl(PPGETTIME)", arg3,
+ sizeof(struct timeval) );
+ break;
+
/* We don't have any specific information on it, so
try to do something reasonable based on direction and
@@ -3863,4 +3945,47 @@ POST(ioctl)
#endif
+ case PPCLAIM:
+ case PPEXCL:
+ case PPYIELD:
+ case PPRELEASE:
+ case PPSETMODE:
+ case PPSETPHASE:
+ case PPSETFLAGS:
+ case PPWDATA:
+ case PPWCONTROL:
+ case PPFCONTROL:
+ case PPDATADIR:
+ case PPNEGOT:
+ case PPWCTLONIRQ:
+ case PPSETTIME:
+ break;
+ case PPGETMODE:
+ VG_TRACK( post_mem_write, arg3, sizeof(int) );
+ break;
+ case PPGETPHASE:
+ VG_TRACK( post_mem_write, arg3, sizeof(int) );
+ break;
+ case PPGETMODES:
+ VG_TRACK( post_mem_write, arg3, sizeof(unsigned int) );
+ break;
+ case PPGETFLAGS:
+ VG_TRACK( post_mem_write, arg3, sizeof(int) );
+ break;
+ case PPRSTATUS:
+ VG_TRACK( post_mem_write, arg3, sizeof(unsigned char) );
+ break;
+ case PPRDATA:
+ VG_TRACK( post_mem_write, arg3, sizeof(unsigned char) );
+ break;
+ case PPRCONTROL:
+ VG_TRACK( post_mem_write, arg3, sizeof(unsigned char) );
+ break;
+ case PPCLRIRQ:
+ VG_TRACK( post_mem_write, arg3, sizeof(int) );
+ break;
+ case PPGETTIME:
+ VG_TRACK( post_mem_write, arg3, sizeof(struct timeval) );
+ break;
+
/* We don't have any specific information on it, so
try to do something reasonable based on direction and
--- valgrind/coregrind/vg_unsafe.h #1.31:1.32
@@ -76,4 +76,5 @@ typedef unsigned short u16;
#include <linux/mii.h> /* for mii_* structs */
#endif
+#include <linux/ppdev.h> /* for PP* ioctls */
#define __USE_LARGEFILE64
|
|
From: Adun R. <adu...@ml...> - 2004-08-16 17:45:43
|
Hold your horses; it seems like you're planning to run atleast part of your code in ring 0. This isn't really what I had in mind. With regards to the thoughts you and I raised, why do you think this is needed? Regards, Rauch Adun. -- Adun R. adu...@ml... |
|
From: Nicholas N. <nj...@ca...> - 2004-08-16 13:02:45
|
On Mon, 16 Aug 2004, Chris January wrote: > Announcing Logrind 2: A program trace framework > > A couple of months ago I finished my final year project: a program trace > framework based on Valgrind and GDB called Logrind 2. Neat. I'll read your report, it looks very good. If you're willing to, I'd recommend changing the name... we've stopped using the "grind" suffix because it becomes pretty meaningless after a while. Hence "Massif", for example. And the '2' is a bit confusing since Logrind 1 wasn't widely known, AFAIK. But it is your tool, you can call it what you want :) You must get pretty huge traces when you use it, right? N |
|
From: Chris J. <ch...@at...> - 2004-08-16 12:33:16
|
Announcing Logrind 2: A program trace framework A couple of months ago I finished my final year project: a program trace framework based on Valgrind and GDB called Logrind 2. The project allows = you to run a program under GDB and trace the program's execution using a = skin for Valgrind. You may debug the program as usual using GDB (the project = adds live debugging support to Valgrind) and execute SQL queries over the program's execution trace. Valgrind's suppression mechanism was extended = to allow the user to control what elements of the program should be traced (e.g. memory writes, function calls). The program trace schema supports multiple sources and can be used to compare runs (and hence used for = delta debugging). Logrind 2 also supports random access navigation of the = program trace allowing you to 'go back in time' to an earlier point in the = program's execution. Sources may be downloaded from here: http://www.atomice.com/logrind2.html The version of Valgrind included is a fork of Valgrind 2.0 but I hope to update it to the latest sources when they stabilise more. Chris January -- http://www.atomice.com=20 |
|
From: Tom H. <th...@cy...> - 2004-08-16 03:04:49
|
Nightly build on standard ( Red Hat 7.2 ) started at 2004-08-16 03:00:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow badaddrvalue: valgrind -q ./badaddrvalue badfree-2trace: valgrind --num-callers=2 -q ./badfree badfree: valgrind -q ./badfree badjump: valgrind ./badjump badloop: valgrind -q ./badloop badrw: valgrind -q ./badrw brk: valgrind ./brk buflen_check: valgrind -q ./buflen_check clientperm: valgrind -q ./clientperm custom_alloc: valgrind -q ./custom_alloc doublefree: valgrind -q ./doublefree error_counts: valgrind --log-fd=-1 ./error_counts errs1: valgrind -q ./errs1 execve: valgrind -q ./execve execve2: valgrind -q --trace-children=yes ./execve2 exitprog: valgrind -q ./exitprog fpeflags: valgrind -q ./fpeflags fprw: valgrind -q ./fprw Could not read `fprw.stderr.exp' make: *** [regtest] Error 2 |
|
From: <js...@ac...> - 2004-08-16 02:55:30
|
Nightly build on phoenix ( SuSE 9.1 ) started at 2004-08-16 03:50:00 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow sem: valgrind ./sem semlimit: valgrind ./semlimit sha1_test: valgrind ./sha1_test shortpush: valgrind ./shortpush shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 173 tests, 4 stderr failures, 0 stdout failures ================= corecheck/tests/as_mmap (stderr) corecheck/tests/fdleak_fcntl (stderr) memcheck/tests/writev (stderr) memcheck/tests/zeropage (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <to...@co...> - 2004-08-16 02:40:06
|
Nightly build on dunsmere ( Fedora Core 2 ) started at 2004-08-16 03:20:01 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 178 tests, 8 stderr failures, 1 stdout failure ================= corecheck/tests/fdleak_cmsg (stderr) corecheck/tests/fdleak_fcntl (stderr) corecheck/tests/fdleak_ipv4 (stderr) corecheck/tests/fdleak_socketpair (stderr) memcheck/tests/buflen_check (stderr) memcheck/tests/execve (stderr) memcheck/tests/execve2 (stderr) memcheck/tests/writev (stderr) none/tests/exec-sigmask (stdout) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2004-08-16 02:19:52
|
Nightly build on audi ( Red Hat 9 ) started at 2004-08-16 03:15:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 178 tests, 8 stderr failures, 0 stdout failures ================= corecheck/tests/fdleak_cmsg (stderr) corecheck/tests/fdleak_fcntl (stderr) corecheck/tests/fdleak_ipv4 (stderr) corecheck/tests/fdleak_socketpair (stderr) memcheck/tests/buflen_check (stderr) memcheck/tests/execve (stderr) memcheck/tests/execve2 (stderr) memcheck/tests/writev (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2004-08-16 02:13:19
|
Nightly build on ginetta ( Red Hat 8.0 ) started at 2004-08-16 03:10:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow seg_override: valgrind ./seg_override sem: valgrind ./sem semlimit: valgrind ./semlimit sha1_test: valgrind ./sha1_test shortpush: valgrind ./shortpush shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 178 tests, 3 stderr failures, 0 stdout failures ================= helgrind/tests/race (stderr) helgrind/tests/race2 (stderr) memcheck/tests/writev (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2004-08-16 02:08:20
|
Nightly build on alvis ( Red Hat 7.3 ) started at 2004-08-16 03:05:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 178 tests, 9 stderr failures, 1 stdout failure ================= addrcheck/tests/toobig-allocs (stderr) helgrind/tests/deadlock (stderr) helgrind/tests/race (stderr) helgrind/tests/race2 (stderr) memcheck/tests/badjump (stderr) memcheck/tests/brk (stderr) memcheck/tests/error_counts (stdout) memcheck/tests/new_nothrow (stderr) memcheck/tests/toobig-allocs (stderr) memcheck/tests/writev (stderr) make: *** [regtest] Error 1 |
|
From: KJK::Hyperion <no...@li...> - 2004-08-16 00:29:20
|
(hope this gets to the list, my STMP has been blacklisted somewhere) At 13.05 13/08/2004, Adun R. wrote: >When we run the process, we can hide it, but from whom? we can only hope it never happens (it could make us completely lose control of the client). Or page-guard everything even vaguely looking like executable memory >Do you suggest to hook the APC set-up? they cause uncontrolled and unpredictable jumps, totally out of the JIT's control. Since they're easy to catch (single dispatcher function at a known location), sure I do. Other such "abnormal" re-entry points to consider are KiRaiseUserExceptionDispatcher (lets a kernel-mode driver call RtlRaiseStatus in an user-mode thread), KiUserCallbackDispatcher (kernel-to-user callback, mainly used to call user-defined callbacks - e.g. custom menu rendering - while the thread is spinning - in kernel mode - in the modal menu loop) and KiUserExceptionDispatcher (dispatches an user-mode exception raised by the current thread through VEH and/or SEH) >This is the general idea. We can also recompile the entire client process >code [thus adding the valdgrind validating/profiling features], copy it >into the client process address space, and run it from there hmmm, this is a lot to take in. Now ideas just keep popping up in my head. We could also run all of the client's code in Valgrind's process and flush the shadow state (registers, virtual memory) into the actual process/threads at certain points (for example on system calls). This will also bring us a lot closer to the current Valgrind design, e.g. the Valgrind-managed RR scheduler will become possible (will this stay? the latest discussions seem to suggest it isn't) I'm still a bit worried about the performance hit of repeated inter-process memory copyies, but maybe, by hooking the appropriate system calls, we can emulate the allocation of private virtual memory with the mapping of unnamed shared memory: Valgrind could then access a lot (still not all) of the client process's memory without a single context switch >[after we hook the IAT and the change SYSENTER/INT 0X2E calls in the >recompiled code into a set of instructions that we'll assure our control] IAT hooking isn't necessary. We're going to hook at a much lower level >Ok. [won't a multi-threaded version of the crt will do the trick?] nope, it will still share global state with the client (if the client uses it), and anyway I can't imagine people will accept a Valgrind you can't write GUI tools for. In general, FV is not an option on Windows. Most subsystems involve state kept in sync between user-mode and kernel-mode components - one kernel process equals one process equals one main executable |