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
(6) |
3
(1) |
4
(1) |
5
|
|
6
|
7
|
8
(1) |
9
|
10
|
11
(4) |
12
(1) |
|
13
|
14
(1) |
15
|
16
|
17
|
18
|
19
|
|
20
|
21
|
22
|
23
|
24
(1) |
25
(4) |
26
(4) |
|
27
(5) |
28
|
29
(2) |
30
|
31
(1) |
|
|
|
From: Ed M. <em...@fr...> - 2019-01-03 15:55:33
|
On Wed, 2 Jan 2019 at 10:31, Ivo Raisr <iv...@iv...> wrote: > > Ed, don't be fooled by this appearance. > Solaris port was made available for review in several patches (I > believe 8 or 9). I've fixed up a few more issues, and started working on curating the changes into more reasonably reviewable pieces. Current WIP is in the "freebsd.20190103" branch - I'll try to keep the patch set rebased on upstream and will start a new branch when rebasing. https://github.com/FreeBSDFoundation/valgrind/tree/freebsd.20190103 Work can be followed in PR 208531 https://bugs.kde.org/show_bug.cgi?id=208531 |
|
From: Ivo R. <iv...@iv...> - 2019-01-02 15:31:31
|
> One concern I had is that this has been maintained as a monolithic > patch and isn't broken up into smaller changes, but I noticed that > e.g. the Solaris port was added in a single commit (ac60633d) so > presumably the same approach can be taken here. Ed, don't be fooled by this appearance. Solaris port was made available for review in several patches (I believe 8 or 9). The actual integration happened as one commit, yes, but review was done on the smaller patch files. I. |
|
From: Ed M. <em...@fr...> - 2019-01-02 14:39:13
|
On Wed, 2 Jan 2019 at 08:08, Philippe Waroquiers <phi...@sk...> wrote: > ... >> https://github.com/FreeBSDFoundation/valgrind/tree/freebsd.rebase > ... > > That all looks like a big pile of work ! > I hope it will be integrated ... > To be discussed with Julian, and I guess the bottleneck will > be the review bandwidth :(. Indeed, at least 30 people have contributed to maintaining this over the last fifteen years. One concern I had is that this has been maintained as a monolithic patch and isn't broken up into smaller changes, but I noticed that e.g. the Solaris port was added in a single commit (ac60633d) so presumably the same approach can be taken here. > I just scanned the diff very quickly, and as far as I can see, > the changes in the common files looks usually small/isolated. Thanks for the quick look. Indeed, the changes are mostly contained to FreeBSD; I did have to adjust two or three cases where these changes broke the build on non-FreeBSD. > At that stage, only a minor comment: as far as I can see, a bunch > of files specific to freebsd were created by taking a copy of the > linux files, but the header and trailer of these files still mention > linux and/or an incorrect machine, which is confusing. Indeed, I'll address those shortly. > What is the status of the regression tests ? There's some ways to go - Phil's recent results were: == 599 tests, 203 stderr failures, 68 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == > Note that to run a daily build+regression tests, if/when integrated > upstream, you could possibly make use of the gcc compile farm. > See https://cfarm.tetaneutral.net/machines/list/ Thanks. I have a machine which provides a buildbot for LLDB on FreeBSD and can probably build Valgrind on there too, but it's good to have additional options. |
|
From: Philippe W. <phi...@sk...> - 2019-01-02 13:07:20
|
On Tue, 2019-01-01 at 23:56 -0500, Ed Maste wrote: > On Fri, 9 Mar 2018 at 16:18, Phil Longstaff <plo...@sa...> wrote: > > > > OK. I’m not completely up-to-date with today’s valgrind source changes, but please clone my repository and make your changes on the freebsd branch. > > A quick status update - I've rebased the work in progress, fixed a few > minor issues, and pushed to a 'freebsd.rebase' branch in the FreeBSD > Foundation's GitHub repository, at > https://github.com/FreeBSDFoundation/valgrind/tree/freebsd.rebase > > Additional testing, as well as fixes for regression tests, are very welcome. > > The current diff is also available at > https://people.freebsd.org/~emaste/valgrind/valgrind-freebsd-20190101.diff That all looks like a big pile of work ! I hope it will be integrated ... To be discussed with Julian, and I guess the bottleneck will be the review bandwidth :(. I just scanned the diff very quickly, and as far as I can see, the changes in the common files looks usually small/isolated. At that stage, only a minor comment: as far as I can see, a bunch of files specific to freebsd were created by taking a copy of the linux files, but the header and trailer of these files still mention linux and/or an incorrect machine, which is confusing. For example, vki/vki-machine-types-amd64-freebsd.h starts with: +/*--- x86/Linux-specific kernel interface: posix types. ---*/ +/*--- vki_posixtypes-x86-linux.h ---*/ There are a bunch of other files to fix similarly, e.g. m_syswrap/syswrap-freebsd-variants.c, ... What is the status of the regression tests ? Note that to run a daily build+regression tests, if/when integrated upstream, you could possibly make use of the gcc compile farm. See https://cfarm.tetaneutral.net/machines/list/ Philippe |
|
From: rajesh s. <inf...@gm...> - 2019-01-02 07:27:18
|
Hi All, I reached to Cavium toolchain team for this issues but got a response saying that they got the binaries from valgrind and included it as part of SDK . Could someone from valgrind team provide binaries for CN70XX and if possible provide the details steps to build the valgrind for our mips architecture with CAVIUM tool chain ? I would like to say thanks for all your support. Thanks, Rajesh On Fri, Nov 23, 2018 at 5:09 AM Petar Jovanovic <mip...@gm...> wrote: > On Thu, Nov 22, 2018 at 5:24 PM rajesh singh <inf...@gm...> > wrote: > > > > Hi John Reiser, > > > > Thanks for reply and information. > > > > > > I am new with this valgrind and glibc library. I am not able to > understand how to resolve this issue. > > Is this issue dependent on libc library or some other issue means why > this terminated before main() function ? > > > > Could you please help me about how to resolve this issue ? > > > > I would like to say thanks for your help. > > > > Thanks, > > Rajesh > > > > On Thu, Nov 22, 2018 at 8:20 PM John Reiser <jr...@bi...> > wrote: > >> > >> > ==31467== Process terminating with default action of signal 10 > (SIGBUS) > >> > ==31467== at 0x40B7EE4: __ctype_init (in /lib64/libc-2.16.so < > http://libc-2.16.so>) > >> > ==31467== by 0x40A8C8C: _init (in /lib64/libc-2.16.so < > http://libc-2.16.so>) > >> > ==31467== by 0x40129D8: call_init (in /lib64/ld-2.16.so < > http://ld-2.16.so>) > >> > ==31467== by 0x4012BC8: _dl_init (in /lib64/ld-2.16.so < > http://ld-2.16.so>) > >> > ==31467== by 0x400328C: _dl_start_user (in /lib64/ld-2.16.so < > http://ld-2.16.so>) > >> > ==31467== Invalid read of size 4 > >> > ==31467== at 0x4019508: __dl_runtime_resolve (in /lib64/ld-2.16.so > <http://ld-2.16.so>) > >> > ==31467== by 0x40192D8: _dl_runtime_resolve (in /lib64/ld-2.16.so > <http://ld-2.16.so>) > >> > ==31467== Address 0xffffffffffff8900 is not stack'd, malloc'd or > (recently) free'd > >> > ==31467== > >> > ==31467== > >> > ==31467== Process terminating with default action of signal 10 > (SIGBUS) > >> > ==31467== at 0x4019508: __dl_runtime_resolve (in /lib64/ld-2.16.so > <http://ld-2.16.so>) > >> > ==31467== by 0x40192D8: _dl_runtime_resolve (in /lib64/ld-2.16.so > <http://ld-2.16.so>) > >> > >> The code in main() never was executed. _dl_start_user is a glibc > routine > >> which runs before the first instruction of main(). The SIGBUS from > trying > >> to fetch from address 0xffffffffffff8900 terminated the program before > main(). > >> > >> > > There is a daily buildbot that runs Valgrind on Cavium boards, and as > of today, all tests pass. > Here is a log from the yesterday's testing: > > Testing Valgrind on: > cavium-02 - mips64r2 BE Linux 4.1.0-dirty glibc 2.13 > 27fe223 Add support for Iop_{Sar,Shr}8 on ppc. > --expensive-definedness-checks=yes needs them. > VEX/priv/host_ppc_isel.c > > == 625 tests, 0 stderr failures, 0 stdout failures, 0 stderrB > failures, 0 stdoutB failures, 0 post failures == > > So it is either to your toolchain or the system. It would not hurt if > you updated your toolchain and the system itself. > > P. > |
|
From: Ed M. <em...@fr...> - 2019-01-02 04:56:45
|
On Fri, 9 Mar 2018 at 16:18, Phil Longstaff <plo...@sa...> wrote: > > OK. I’m not completely up-to-date with today’s valgrind source changes, but please clone my repository and make your changes on the freebsd branch. A quick status update - I've rebased the work in progress, fixed a few minor issues, and pushed to a 'freebsd.rebase' branch in the FreeBSD Foundation's GitHub repository, at https://github.com/FreeBSDFoundation/valgrind/tree/freebsd.rebase Additional testing, as well as fixes for regression tests, are very welcome. The current diff is also available at https://people.freebsd.org/~emaste/valgrind/valgrind-freebsd-20190101.diff |
|
From: Ed M. <em...@fr...> - 2019-01-02 02:12:15
|
On Thu, 22 Feb 2018 at 12:18, Ivo Raisr <iv...@iv...> wrote: > > But what is more needed is to setup a FreeBSD buildbot and maintain it. > There are simple instructions in Valgrind repo how to do it > (nightly/README.txt). For now I've been exploring Cirrus-CI as a hosted CI service for the ongoing work on upstreaming the FreeBSD port - see e.g. results at https://cirrus-ci.com/build/5675722230202368 Of course we can also set up a buildbot connecting to the main CI system. |