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) |
2
|
|
3
(1) |
4
|
5
|
6
|
7
|
8
|
9
|
|
10
|
11
(3) |
12
|
13
(1) |
14
|
15
(1) |
16
|
|
17
|
18
|
19
|
20
(1) |
21
|
22
|
23
|
|
24
|
25
|
26
|
27
|
28
|
29
(2) |
30
|
|
31
|
|
|
|
|
|
|
|
From: Nicholas N. <nj...@ca...> - 2003-08-11 13:51:52
|
On 11 Aug 2003, Tom Hughes wrote: > > [~/grind/massif] echo "foo -> bar" | valgrind sed -e 's/^.* -> /b/' > > [ snipped output ] > > > The problem is the spaces in the quoted string; the string gets broken up > > into 3 arguments; this happens in the "valgrind" startup script. I've > > tried to stop this, fiddling with the quotes, using $* instead of $@, but > > it's beyond my understanding of shell quoting rules. Does anyone have any > > suggestions? > > It seems to work for me, which is what I would expect as all the > script is doing is shifting the argument list (although not in this > case as there are switches for valgrind) and then using exec "$@" > which is supposed to preserve the existing word boundaries. You're completely right. My invocation of Valgrind was via a bash function; in that function I was using inappropriate quoting :( Apologies for the distraction, thanks for the correction. N |
|
From: Tom H. <th...@cy...> - 2003-08-11 12:23:18
|
In message <Pin...@gr...>
Nicholas Nethercote <nj...@ca...> wrote:
> [~/grind/massif] echo "foo -> bar" | valgrind sed -e 's/^.* -> /b/'
[ snipped output ]
> The problem is the spaces in the quoted string; the string gets broken up
> into 3 arguments; this happens in the "valgrind" startup script. I've
> tried to stop this, fiddling with the quotes, using $* instead of $@, but
> it's beyond my understanding of shell quoting rules. Does anyone have any
> suggestions?
It seems to work for me, which is what I would expect as all the
script is doing is shifting the argument list (although not in this
case as there are switches for valgrind) and then using exec "$@"
which is supposed to preserve the existing word boundaries. Here's
the output I get:
audi [~] % echo "foo -> bar" | valgrind sed -e 's/^.* -> /b/'
==25239== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==25239== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward.
==25239== Using valgrind-20030716, a program supervision framework for x86-linux.
==25239== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward.
==25239== Estimated CPU clock rate is 2019 MHz
==25239== For more details, rerun with: -v
==25239==
bbar
==25239== Warning: client attempted to close Valgrind's logfile fd (2).
==25239== Use --logfile-fd=<number> to select an alternative logfile fd.
==25239== discard syms in /usr/lib/locale/locale-archive due to munmap()
==25239==
==25239== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==25239== malloc/free: in use at exit: 13647 bytes in 97 blocks.
==25239== malloc/free: 232 allocs, 135 frees, 85411 bytes allocated.
==25239== For a detailed leak analysis, rerun with: --leak-check=yes
==25239== For counts of detected errors, rerun with: -v
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Nicholas N. <nj...@ca...> - 2003-08-11 12:02:45
|
Hi, I've found a problem with Valgrind's handling of quoted command line arguments. It's pretty obscure, I guess that's why nobody's complained before. Compare these two commands, with and without Valgrind: [~/grind/massif] echo "foo -> bar" | sed -e 's/^.* -> /b/' bbar [~/grind/massif] echo "foo -> bar" | valgrind sed -e 's/^.* -> /b/' ==26593== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==26593== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==26593== Using valgrind-20030716, a program supervision framework for x86-linux. ==26593== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==26593== Estimated CPU clock rate is 1404 MHz ==26593== For more details, rerun with: -v ==26593== sed: -e expression #1, char 5: Unterminated `s' command ==26593== ==26593== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==26593== malloc/free: in use at exit: 4884 bytes in 3 blocks. ==26593== malloc/free: 44 allocs, 41 frees, 9247 bytes allocated. ==26593== For a detailed leak analysis, rerun with: --leak-check=yes ==26593== For counts of detected errors, rerun with: -v The problem is the spaces in the quoted string; the string gets broken up into 3 arguments; this happens in the "valgrind" startup script. I've tried to stop this, fiddling with the quotes, using $* instead of $@, but it's beyond my understanding of shell quoting rules. Does anyone have any suggestions? Thanks. N |