On Sun, Jan 13, 2008 at 01:47:58AM +, [EMAIL PROTECTED] wrote:
> +++ branches/DATASYMS/coregrind/m_libcbase.c 2008-01-13 01:47:56 UTC (rev
> 7339)
> @@ -563,13 +563,14 @@
> +Int VG_(log2) ( UInt x )
> {
> Int i;
> /* Any more than 32 and we overflow anyway... */
> for (i = 0; i
On Mon, Nov 26, 2007 at 09:34:32PM +, [EMAIL PROTECTED] wrote:
> Author: sewardj
> Date: 2007-11-26 21:34:30 + (Mon, 26 Nov 2007)
> New Revision: 7228
>
> Log:
> drd: make the build silent regardless of platform, and abort at
> startup with a message if a not supported platform, like
On Sat, Nov 17, 2007 at 03:41:24AM +0100, Julian Seward wrote:
> On Saturday 17 November 2007 01:13, Nicholas Nethercote wrote:
> > That sounds ok. In summary:
> >
> > --log-file=
>
> That sounds good to me. With patterns
>
> %p process ID
> %q(VAR) contents of $VAR
>
> I would pr
On Sat, Nov 03, 2007 at 07:59:38AM +1100, Nicholas Nethercote wrote:
> On Fri, 2 Nov 2007, Oswald Buddenhagen wrote:
>> for *way* more clarity
>> and less bloat i'd suggest writing the actual expression as
>> update_alloc_stats(heap_szB_delta +
>> (SizeT)cl
On Fri, Nov 02, 2007 at 08:56:08AM -0700, Dave Nomura wrote:
> Is it possible to run an x86 valgrind on a PPC program? If so, how
> would you do it?
>
so you want a cross-executing valgrind ...
while i think vex would have no major problems with it (give or take
some minor adjustments), i'm prett
On Fri, Nov 02, 2007 at 04:12:50AM +, [EMAIL PROTECTED] wrote:
> Author: njn
> -static UInt clo_heap_admin = 8;
> + // clo_heap_admin is deliberately a word-sized type. At one point it was
> + // a UInt, but this caused problems on 64-bit machines when it was
> + // multiplied by a
On Thu, Nov 01, 2007 at 10:58:04AM +, [EMAIL PROTECTED] wrote:
> Author: njn
> + VG_(tool_panic)(
>
i for one would make the build break at an early stage (configure).
fwiw, another option would be recording the last [EMAIL PROTECTED] of merged
branches in some file in trunk and afterwards
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
>
