On 10/5/07, Nicholas Nethercote <[EMAIL PROTECTED]> wrote:
> Julian and I have been discussing for a while the idea of creating a
> category of "experimental" tools in the Valgrind source tree. These
> would be tools that are not necessarily mature, but may be of interest
> to people. This would
Author: njn
Date: 2007-10-05 06:16:33 +0100 (Fri, 05 Oct 2007)
New Revision: 6954
Log:
various minor cleanups
Modified:
branches/MASSIF2/massif/ms_main.c
Modified: branches/MASSIF2/massif/ms_main.c
===
--- branches/MASSIF2/massi
Author: njn
Date: 2007-10-05 06:06:49 +0100 (Fri, 05 Oct 2007)
New Revision: 6953
Log:
Remove unnecessary whitespace at end of lines.
Modified:
branches/MASSIF2/massif/ms_main.c
Modified: branches/MASSIF2/massif/ms_main.c
===
--
Author: njn
Date: 2007-10-05 06:00:13 +0100 (Fri, 05 Oct 2007)
New Revision: 6952
Log:
- Added snapshot 'kind' field, in preparation for peak-taking.
- Refactored 'take_snapshot'.
Modified:
branches/MASSIF2/massif/ms_main.c
Modified: branches/MASSIF2/massif/ms_main.c
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-10-05 03:15:02 BST
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ..
Nightly build on dellow ( x86_64, Fedora 7 ) started at 2007-10-05 03:10:04 BST
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... f
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2007-10-05 03:05:06 BST
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ...
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-10-05 03:00:03
BST
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
On Thu, 4 Oct 2007, Dirk Mueller wrote:
> My primary concern was to ensure that no format string mismatches occur that
> could cause strange misbehaviour or crashes on rare (possible not regression
> tested) scenarios.
I've been annoyed several times in my recent Massif2 work with incorrect
form
On Thu, 4 Oct 2007, Dirk Mueller wrote:
> On Wednesday, 3. October 2007, Julian Seward wrote:
>
>> Addr/Word/UWord args with %p formats, either by casting the arg to void*
>> or changing the format to 0x%lx.
>
> I'm currently unable to decide which route to take. We can represent Addr in
> two way
Hi,
Julian and I have been discussing for a while the idea of creating a
category of "experimental" tools in the Valgrind source tree. These
would be tools that are not necessarily mature, but may be of interest
to people. This would make it much easier for users to try out
experimental tools -
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-10-05 02:00:01 CEST
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ...
Author: dirk
Date: 2007-10-05 00:12:12 +0100 (Fri, 05 Oct 2007)
New Revision: 6951
Log:
fix format strings for the tools (except for helgrind)
Modified:
branches/FORMATCHECK/callgrind/bb.c
branches/FORMATCHECK/callgrind/bbcc.c
branches/FORMATCHECK/callgrind/callstack.c
branches/FORMAT
Author: dirk
Date: 2007-10-04 23:48:53 +0100 (Thu, 04 Oct 2007)
New Revision: 6950
Log:
fix format strings for coregrind/
Modified:
branches/FORMATCHECK/coregrind/m_debuginfo/debuginfo.c
branches/FORMATCHECK/coregrind/m_debuginfo/readdwarf.c
branches/FORMATCHECK/coregrind/m_debuginfo/rea
Author: dirk
Date: 2007-10-04 22:38:47 +0100 (Thu, 04 Oct 2007)
New Revision: 6949
Log:
implement '#' modifier for 'x' and 'X' at least
Modified:
branches/FORMATCHECK/coregrind/m_debuglog.c
Modified: branches/FORMATCHECK/coregrind/m_debuglog.c
Author: dirk
Date: 2007-10-04 22:36:40 +0100 (Thu, 04 Oct 2007)
New Revision: 6948
Log:
readd right adjustment.
Modified:
trunk/coregrind/m_stacktrace.c
Modified: trunk/coregrind/m_stacktrace.c
===
--- trunk/coregrind/m_stacktra
Author: dirk
Date: 2007-10-04 22:35:21 +0100 (Thu, 04 Oct 2007)
New Revision: 6947
Log:
revert format checking warnings from trunk, will
be done in a branch
Modified:
trunk/include/pub_tool_libcprint.h
Modified: trunk/include/pub_tool_libcprint.h
=
Author: dirk
Date: 2007-10-04 22:34:06 +0100 (Thu, 04 Oct 2007)
New Revision: 6946
Log:
create format checking branch
Added:
branches/FORMATCHECK/
Copied: branches/FORMATCHECK (from rev 6945, trunk)
-
This SF.net email
On Wednesday, 3. October 2007, Julian Seward wrote:
> Addr/Word/UWord args with %p formats, either by casting the arg to void*
> or changing the format to 0x%lx.
I'm currently unable to decide which route to take. We can represent Addr in
two ways:
VG_(printf)("%#lx", ..)
or
VG_(printf)(
On Thursday, 4. October 2007, Nicholas Nethercote wrote:
> Making things more ANSI would be good
My primary concern was to ensure that no format string mismatches occur that
could cause strange misbehaviour or crashes on rare (possible not regression
tested) scenarios.
> , but then the ',' pr
On Monday, 1. October 2007, Bart Van Assche wrote:
> you changed the
> format string %08p into %p. As a result, the printed pointers are no longer
> right-aligned.
True. It was my impression that %p does this by default, but it seems I was
wrong. I'll correct this mistake shortly, thanks for po
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2007-10-04 09:00:01 BST
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ..
On 10/4/07, Oswald Buddenhagen <[EMAIL PROTECTED]> wrote:
>
> On Thu, Oct 04, 2007 at 09:31:28AM +1000, Nicholas Nethercote wrote:
> > Making things more ANSI would be good, but then the ',' prefix is also
> > extremely useful -- it inserts commas into printed numbers, eg. prints
> > "1,234,567" in
On Thu, Oct 04, 2007 at 09:31:28AM +1000, Nicholas Nethercote wrote:
> Making things more ANSI would be good, but then the ',' prefix is also
> extremely useful -- it inserts commas into printed numbers, eg. prints
> "1,234,567" instead of "1234567". Any ideas for how to get the best of both
>
24 matches
Mail list logo
