Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-01-08 03:15:10 GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ..
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-01-08 03:05:13 GMT
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 8 ) started at 2008-01-08 03:10:04 GMT
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 gill ( x86_64, Fedora Core 2 ) started at 2008-01-08 03:00:04
GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
Author: sewardj
Date: 2008-01-08 00:36:15 + (Tue, 08 Jan 2008)
New Revision: 7321
Log:
ppc64-linux specific followup to r7320.
Modified:
branches/DATASYMS/coregrind/m_debuginfo/readelf.c
Modified: branches/DATASYMS/coregrind/m_debuginfo/readelf.c
=
Author: sewardj
Date: 2008-01-08 00:09:03 + (Tue, 08 Jan 2008)
New Revision: 7320
Log:
Rename the type SegInfo (which it just isn't) to DebugInfo, a more
appropriate name. Also, rename and reorder some fields in DebugInfo.
Modified:
branches/DATASYMS/callgrind/bb.c
branches/DATASYMS/ca
On Dec 3, 2007 1:35 PM, Julian Seward <[EMAIL PROTECTED]> wrote:
> On Monday 03 December 2007 09:47, Tom Hughes wrote:
> > In message <[EMAIL PROTECTED]>
> >
> > Nicholas Nethercote <[EMAIL PROTECTED]> wrote:
> > > I can either change the script to run 'make exp-regtest' -- which will
> > >
Author: sewardj
Date: 2008-01-07 19:24:26 + (Mon, 07 Jan 2008)
New Revision: 7319
Log:
Commit initial framework changes aimed at making data symbol reading
and .got/.plt identification work properly on Linux.
The basic observation is that until now, Valgrind has waited until an
ELF file is ma
Tom Hughes wrote:
On 03/01/2008, Nicholas Nethercote <[EMAIL PROTECTED]> wrote:
If a kernel type isn't present, a vki_* version should be added.
See the comment at the top of include/vki/vki-linux.h.
But don't trust the man pages, they mostly describe glibc's wrappers for the
syscalls. These
On Jan 7, 2008 8:50 AM, Yossi Kreinin <[EMAIL PROTECTED]> wrote:
> What I need is to support people using Windows as their development machine.
Call me crazy, but I think the best way to do that
is to get their windows development tools running
100% under Wine :-)
- Dan
--
Looking at the wine preloader's travails with reserving address space,
including http://www.nabble.com/Valgrind-and-Wine-td14442642.html ,
here are some thoughts.
Julian's comment about changing valt_load_address_normal certainly
is part of the solution. Try 0x6000 (1.6GB) as the value, to a
On Jan 7, 2008 6:32 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
>
> Y'know, it might be more productive for
> you get simply use valgrind on wine.
>
> That solves the problem of instrumenting Windows binaries. What I need is
to support people using Windows as their development machine. I'm mostly
int
On Jan 7, 2008 8:28 AM, Yossi Kreinin <[EMAIL PROTECTED]> wrote:
> I think I want to try to port valgrind to Windows.
Y'know, it might be more productive for
you get simply use valgrind on wine. That's
been working for a couple years, and is starting
to be rather useful.
How about you try that o
Hi!
I think I want to try to port valgrind to Windows. My knowledge of the
code base is pretty basic - enough to implement skins that are useful
to me and I'd like them to run under Windows. Not enough to estimate
how stupid the idea of trying such a port is though.
The "Supported Platforms" page
14 matches
Mail list logo
