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
|
2
|
3
|
4
|
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
|
12
|
13
|
14
|
15
|
16
|
17
(1) |
18
|
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
|
26
|
27
(2) |
28
(2) |
29
(1) |
30
|
31
|
|
|
From: Josef W. <Jos...@gm...> - 2003-01-29 00:04:54
|
On Tuesday 28 January 2003 21:43, Nicholas Nethercote wrote: > On Mon, 27 Jan 2003, Josef Weidendorfer wrote: > > Can you have a short look at this? > > Is this the correct way for a third-party valgrind skin source package? > > > > * Valgrind should install header files for compiling skins. > > I had to add them to the skin sources :-( > > Um, I hadn't given this a great deal of thought. I think I was imagining > something simpler, eg: > - add a directory under valgrind/ containing the skin's code and > Makefile.am - add the skin's name to configure.in and Makefile.am (by hand) But this makes the process of distributing valgrind skins separate from valgrind core impossible. I think the valgrind core is much like a library for skins, and we should allow developing skins on a machine with a binary installation of valgrind. I saw the problem with precompiled packages for Debian and my calltree patch with Valgrind 1.0.x: The only possible way to get my patch was to remove the valgrind package and install the patched one. It would be much better to simple install a further package for a third-party skin. And this involves separate source packages, too. You already made skin development independent from valgrind versions by introducing a skin interface version. Thus, skins should be distributable independent from valgrind releases. > and then it all works. I think; that's how I've been doing things when > writing new skins. That way there's no problems with installing headers > because they're all in the one place. I wasn't expecting to have > configure.in and all that for a skin. I realise adding the name to > configure.in and Makefile.am by hand isn't ideal, but it seems to me the > most straightforward option... See above. Problems come up if a skin developer doesn't have access to valgrind CVS and wants to distribute his skin ;-) > > * I install a "calltree" script which is almost a simple copy of the > > valgrind loader script. Only difference: It defaults to a skin with name > > `basename $0`. As the script is called "calltree", it defaults to skin > > "vgskin_calltree.so". Is this change sensible for the valgrind script > > itself? > > Problem: "calltree -h" gives help for the valgrind command, and not the > > calltree script. Can we define a variable "VALGRIND_SCRIPT" with the > > script name? Thus, valgrind could put out the correct help text. > > > > Valgrind 1.9.x should supply a "cachegrind" script, too. > > If a user updates from 1.0.x to 1.9.x he will assume that executing > > "cachegrind" is still valid (I already got a bug report regarding this!). > > I was hoping to get away from the need for multiple startup scripts with > the --skin= option. The removal of the 'cachegrind' script was deliberate > (probably should have been documented). Having lots of different startup > scripts that are almost the same is not good. I like the --skin way > better, and if you get sick of typing it for your favourite skin it's not > hard to define an alias for it. This was just a suggestion. I like it the other way around ;-) You don't have to have multiple startup scripts. With 'basename $0' as skin it would be enough to make (hard or soft) symlinks to the valgrind script named by the skin. > As for the -h option, if a skin uses command line args, the function > SK_(usage)() allows it to describe them. Is this not enough for your > purposes? Of course. I only thought about a solution to forward the name of a startup script to the valgrind core... > > For the rewrite of the calltree skin, I want to add address mappings of > > ELF objects to cachegrind.out (To allow usage of "nm" in KCachegrind for > > assembler source annotations). > > Can we add the following function to coregrind/vg_symtab2.c for this? > > > > SegInfo* VG_(get_obj) ( Addr a ) > > Sure, done. Thanks. Josef > N > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |