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
(18) |
2
(35) |
3
(34) |
4
(25) |
5
(16) |
6
(32) |
|
7
(7) |
8
(13) |
9
(20) |
10
(17) |
11
(10) |
12
(18) |
13
(9) |
|
14
(5) |
15
(26) |
16
(23) |
17
(5) |
18
(1) |
19
(4) |
20
(3) |
|
21
(10) |
22
(13) |
23
(13) |
24
(23) |
25
(30) |
26
(13) |
27
(6) |
|
28
(1) |
29
(16) |
30
(15) |
|
|
|
|
|
From: <sv...@va...> - 2009-06-25 04:16:59
|
Author: njn Date: 2009-06-25 05:16:53 +0100 (Thu, 25 Jun 2009) New Revision: 392 Log: Clarify bug-reporting instructions. Modified: trunk/support/bug_reports.html Modified: trunk/support/bug_reports.html =================================================================== --- trunk/support/bug_reports.html 2009-06-16 06:07:43 UTC (rev 391) +++ trunk/support/bug_reports.html 2009-06-25 04:16:53 UTC (rev 392) @@ -1,55 +1,102 @@ <h1>Bug Reports</h1> +<br/> + +<h2>Before Reporting a Bug</h2> + <p>Before you report a bug, please consult the <a href="/docs/manual/FAQ.html">Frequently Asked Questions</a>. It -contains workarounds for more or less all the failure conditions -for which we know a workaround. This includes a large fraction of -the failures people seem to encounter in practice.</p> +contains workarounds for many of the failure conditions for which we know a +workaround. This includes a large fraction of the failures people seem to +encounter in practice.</p> -<p>If that fails, please file a report using our -<?php echo vglink( 'vgbugsreport' ); ?> page. You can search for existing -bugs using the -<?php echo vglink( 'vgbugsquery' ); ?> page (make sure you choose Valgrind -as the "product"), or see all open bug reports at the +<p>After that, please search to see if the bug has already been reported +using the <?php echo vglink( 'vgbugsquery' ); ?> page (make sure you choose +Valgrind as the "product"), or by viewing all open bug reports at the <?php echo vglink( 'vgbugsopenlist' ); ?> page. Anyone can search the -database, but you need to open a Bugzilla account (instructions are on the -page) to report a bug.</p> +database. Searching requires some effort, but helps avoid duplicates, and +you may find that your problem has already been solved.</p> -<p>Because the Valgrind developers are busy, very busy, -the quality of your bug report can make a big difference in -how soon your bug gets fixed. Following a few simple guidelines -helps us to help you. Here are some resources on -how to write a good bug report:</p> +<h2>Reporting a Bug</h2> + +<p>If you haven't encountered your problem after those steps, please file a +report using our <?php echo vglink( 'vgbugsreport' ); ?> page. You need a +Bugzilla account (instructions for creating one are on the page) to report a +bug.</p> + +<p>The bug report form can be intimidating. Fortunately you don't have to +fill in all the fields. Leave all fields blank except the following:</p> + <ul> + <li><strong>Component:</strong> If the problem is with a specific Valgrind + tool (eg. Memcheck, Cachegrind), select the tool name. If it's a general + problem that appears tool-independent, select "general".</li> + + <li><strong>Version:</strong> The version number is shown when Valgrind + starts up. Only use a "SVN"-suffixed version if you are using code from + the SVN repository.</li> + + <li><strong>Severity:</strong></li> If you are seeing a crash, choose + "crash". If your problem is minor, choose "minor" or "wishlist". + Otherwise, choose "normal". Please leave the "major", "grave" or + "critical" categories to the Valgrind developers to decide. + + <li><strong>Platform:</strong></li> "unspecified" is usually fine; this + field isn't very important. + + <li><strong>OS:</strong> This is auto-filled. Change it if necessary.</li> + + <li><strong>Summary:</strong></li> This is the title of the bug report. + Try to make it precise. E.g. if you get an assertion failure, don't say + "assertion failure"; copy in the actual assertion failure message. + + <li><p><strong>Description:</strong> The most important field. + Please give the following information:</p> + <ul> + <li>The output of <code>uname -a</code>.</li> + <li>The full output you get when you run your program under Valgrind + with the <code>-v</code> flag.</li> + </ul> + Note that a bug is much more likely to be fixed if a Valgrind + developer can reproduce it. So full reproduction steps are very helpful. + Small test cases are even better.</p> +</ul> + +<p>Here are some resources on how to write a good bug report, which can help +your get your problem fixed quicker:</p> +<ul> <li> Eric Raymond's and Rick Moen's <a href="http://www.catb.org/~esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</a></li> <li> mozilla.org's <a href="http://www.mozilla.org/quality/bug-writing-guidelines.html">bug writing guidelines</a></li> <li> Simon Tatham's <a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</a></li> </ul> +<h2>After Reporting a Bug</h2> +<p>All bug reports are read by multiple Valgrind developers. Furthermore, +we try to respond to most bug reports, but we have limited time so this does +not always happen. We may also ask for more information.</p> + +<p>If a bug is confirmed (e.g. we are able to reproduce it) we will usually +change its status from UNCONFORMED to NEW or ASSIGNED. Important bugs will +be given a "target" by developers indicating that they are required/desired +for an upcoming. Note that we don't really use the "priority" field, so it +will usually be "NOR" (normal).</p> + +<p>Once a bug is fixed in the SVN repository, it is changed to RESOLVED. We +do not use the VERIFIED or CLOSED statuses.</p> + +<p>Some bugs are fixed quickly, some take a long time to get fixed, some are +never fixed. Please be patient if your bug is not acted upon quickly. One +great thing about Bugzilla is that, at the very least, bug reports do not +get lost.</p> + + +<h2>Alternatives</h2> + <p>If you have trouble with Bugzilla, or for some reason you don't think Bugzilla is appropriate for your report (although it probably is), contact the <?php echo vglink('vgusers'); ?> -mailing list. We try to respond to most bug reports, but if -we don't, it doesn't mean we are ignoring you; it may well be -that the bug has been reported before.</p> +mailing list. But you may just be told to file a bug in Bugzilla.</p> -<p>When you report a bug, please give the following information:</p> -<ul> - <li>The output of <code>uname -a</code>.</li> - <li>The full output you get when you run your program under Valgrind - with the <code>-v</code> flag.</li> -</ul> - -<p>If you can produce a small test program that exposes the -problem, that would be extremely useful. It is also useful to -include your Linux distro version and glibc version. If you -include all this information, you are much more likely to get a -useful response.</p> - -<p>Some bugs are fixed quickly, some take a long time to get fixed. -Please be patient if your bug is not acted upon quickly. The great -thing about Bugzilla is that bug reports do not get lost.</p> - |
|
From: Tom H. <th...@cy...> - 2009-06-25 02:47:41
|
Nightly build on lloyd ( x86_64, Fedora 7 ) Started at 2009-06-25 03:05:05 BST Ended at 2009-06-25 03:47:24 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 491 tests, 0 stderr failures, 0 stdout failures, 0 post failures == ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 490 tests, 0 stderr failures, 0 stdout failures, 0 post failures == ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Jun 25 03:26:18 2009 --- new.short Thu Jun 25 03:47:24 2009 *************** *** 8,10 **** ! == 490 tests, 0 stderr failures, 0 stdout failures, 0 post failures == --- 8,10 ---- ! == 491 tests, 0 stderr failures, 0 stdout failures, 0 post failures == |
|
From: Tom H. <th...@cy...> - 2009-06-25 02:46:13
|
Nightly build on vauxhall ( x86_64, Fedora 10 ) Started at 2009-06-25 03:20:03 BST Ended at 2009-06-25 03:46:05 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 500 tests, 0 stderr failures, 0 stdout failures, 0 post failures == ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 499 tests, 0 stderr failures, 0 stdout failures, 0 post failures == ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Jun 25 03:33:11 2009 --- new.short Thu Jun 25 03:46:05 2009 *************** *** 8,10 **** ! == 499 tests, 0 stderr failures, 0 stdout failures, 0 post failures == --- 8,10 ---- ! == 500 tests, 0 stderr failures, 0 stdout failures, 0 post failures == |
|
From: Tom H. <th...@cy...> - 2009-06-25 02:28:43
|
Nightly build on mg ( x86_64, Fedora 9 ) Started at 2009-06-25 03:10:06 BST Ended at 2009-06-25 03:28:33 BST 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 == 497 tests, 0 stderr failures, 1 stdout failure, 0 post failures == none/tests/linux/mremap2 (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 == 496 tests, 0 stderr failures, 1 stdout failure, 0 post failures == none/tests/linux/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Jun 25 03:19:27 2009 --- new.short Thu Jun 25 03:28:33 2009 *************** *** 8,10 **** ! == 496 tests, 0 stderr failures, 1 stdout failure, 0 post failures == none/tests/linux/mremap2 (stdout) --- 8,10 ---- ! == 497 tests, 0 stderr failures, 1 stdout failure, 0 post failures == none/tests/linux/mremap2 (stdout) |
|
From: Samuel B. <na...@gm...> - 2009-06-25 00:09:00
|
Hi. I'm trying to run some DPMI code under DOSEMU under valgrind,
hoping to track down some sort of leak, but valgrind gets stuck on
some of the segmentation-related instructions. For example, trying to
run DJGPP's ls, I get this:
,----
| 0x473600D: lss (%esp,,),%esp
|
| ------ IMark(0x473600D, 4) ------
| PUT(60) = 0x473600D:I32
| t14 = GET:I32(16)
| PUT(16) = LDle:I32(t14)
| PUT(290) = LDle:I16(Add32(t14,0x4:I32))
|
| 0x4736011: vex x86->IR: unhandled instruction bytes: 0x2E 0xFF 0x2D 0x0
| ------ IMark(0x4736011, 0) ------
| PUT(60) = 0x4736011:I32
| PUT(60) = 0x4736011:I32
| goto {NoDecode} 0x4736011:I32
|
| . 0 4736000 17
| . 89 D4 0F A9 0F A1 07 1F 61 83 C4 10 9D 0F B2 24 24
|
| ==13075== Warning: client switching stacks? SP change: 0xbed3e730 --> 0x821dba0
| ==13075== to suppress, use: --max-stackframe=1229845616 or greater
| ==13075== Warning: client switching stacks? SP change: 0x821dbe4 --> 0x760
| ==13075== to suppress, use: --max-stackframe=136434820 or greater
| ==13075== valgrind: Unrecognised instruction at address 0x4736011.
| ==13075== Your program just tried to execute an instruction that Valgrind
| ==13075== did not recognise. There are two possible reasons for this.
| ==13075== 1. Your program has a bug and erroneously jumped to a non-code
| ==13075== location. If you are running Memcheck and you just saw a
| ==13075== warning about a bad jump, it's probably your program's fault.
| ==13075== 2. The instruction is legitimate but Valgrind doesn't handle it,
| ==13075== i.e. it's Valgrind's fault. If you think this is the case or
| ==13075== you are not sure, please let us know and we'll try to fix it.
| ==13075== Either way, Valgrind will now raise a SIGILL signal which will
| ==13075== probably kill your program.
`----
-- and that's AFTER adding support for the LSS instruction to VEX.
It turns out that the unrecognized instruction is some kind of
indirect far jump that ndisasm renders as:
00000000 2EFF2D00010203 jmp dword far [dword cs:0x3020100]
and objdump as:
0: 2e ff 2d 00 01 02 03 ljmp *%cs:0x3020100
(the address part is mostly bogus since I'm just working with the four
bytes that VEX dumped for me, but that shouldn't matter.)
It does not look as if either VEX or valgrind supports having CS refer
to a non-flat segment; how crazy would it be to try to add this?
P.S. The code for LSS should be in
https://code.launchpad.net/~naesten/valgrind/vex-segmented soon; it's
not there quite yet on account of having to push the entire SVN trunk
history of vex, which is taking a bit -- it's been almost ten minutes
already, and the progress bar looks to be at about 50%, though I have
my doubts as to whether or not it means anything.
|