Author: njn
Date: 2008-02-13 05:05:58 + (Wed, 13 Feb 2008)
New Revision: 7405
Log:
Fix minor breakage in 7 tests.
Modified:
trunk/memcheck/tests/addressable.stderr.exp
trunk/memcheck/tests/badjump.stderr.exp
trunk/memcheck/tests/describe-block.stderr.exp
trunk/memcheck/tests/fil
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-02-13 03:15:02 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-02-13 03:05:04 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 aston ( x86_64, Fedora Core 5 ) started at 2008-02-13 03:20:04
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 trojan ( x86_64, Fedora Core 6 ) started at 2008-02-13
03:25:06 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-02-13 03:10:03 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-02-13 03:00:02
GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
On Wednesday 13 February 2008 03:35, Nicholas Nethercote wrote:
> On Wed, 13 Feb 2008, Julian Seward wrote:
> > In addition, I'd bet that most stack frames are a lot smaller
> > than a page, so the caching is also spatially effective: if we
> > know that this frame is safe to poke around in, then i
On Wed, 13 Feb 2008, Julian Seward wrote:
> In addition, I'd bet that most stack frames are a lot smaller
> than a page, so the caching is also spatially effective: if we
> know that this frame is safe to poke around in, then it's likely
> that the next frame is in the same page and so we don't ev
> > * This might give a bit of a performance hit in unwind-
> > intensive programs as the stacks list now has to be searched for
> > each snapshot. I guess we could mostly ameliorate this by the
> > usual trick of incrementally rearranging the list to diffuse
> > frequently-requested entr
On Tuesday 12 February 2008 11:10, Julian Seward wrote:
> > Worth filing a bug for?
>
> I'd say yes, considering it's happening in an unpatched valgrind.
It may or not be related to this:
http://bugs.kde.org/show_bug.cgi?id=156065
J
---
Author: sewardj
Date: 2008-02-12 21:55:15 + (Tue, 12 Feb 2008)
New Revision: 7404
Log:
Start tidying up (non-functional change):
* move stuff to do with Dwarf3 expression evaluation into
d3basics.c, a sane place for it
* get rid of VG_(get_error_tid) introduced in r7375 as it
is not nece
Author: sewardj
Date: 2008-02-12 20:18:11 + (Tue, 12 Feb 2008)
New Revision: 7403
Log:
Format descriptions of data addresses in a better way.
Modified:
branches/DATASYMS/coregrind/m_debuginfo/debuginfo.c
branches/DATASYMS/coregrind/m_debuginfo/priv_tytypes.h
branches/DATASYMS/coregr
On Feb 12, 2008 4:27 AM, Tom Hughes <[EMAIL PROTECTED]> wrote:
>
> exp-drd/tests/tc18_semabuse (stderr)
Hello Tom,
Can you please send me the diff files for this regression test ?
Thanks,
Bart Van Assche.
-
Th
In message <[EMAIL PROTECTED]>
Bart Van Assche <[EMAIL PROTECTED]> wrote:
> On Feb 12, 2008 4:27 AM, Tom Hughes <[EMAIL PROTECTED]> wrote:
>>
>> exp-drd/tests/tc18_semabuse (stderr)
>
> Can you please send me the diff files for this regression test ?
It's asserting - here's t
> Memcheck: mc_leakcheck.c:698 (vgMemCheck_do_detect_memory_leaks):
> Assertion 'lc_shadows[i]->data + lc_shadows[i]->szB <=
> lc_shadows[i+1]->data' failed.
> at report_and_quit (m_libcassert.c:140)
[snip]
> by shutdown_actions_NORETURN (m_main.c:2025)
> by run_a_thread_NORETURN (sy
Author: sewardj
Date: 2008-02-12 13:54:28 + (Tue, 12 Feb 2008)
New Revision: 7402
Log:
* Describe offsets inside variables in terms of source level types,
where possible
* Record declaration coordinates of variables and use them in messages
Modified:
branches/DATASYMS/coregrind/m_deb
In message <[EMAIL PROTECTED]>
Julian Seward <[EMAIL PROTECTED]> wrote:
> * Would it perhaps be prudent to deregister the stack at thread
> exit? Otherwise, the linked list of stacks grows without bound
> (afaics -- VG_(deregister_stack) is only ever called as a result
> of a client
> Worth filing a bug for?
I'd say yes, considering it's happening in an unpatched valgrind.
J
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/
19 matches
Mail list logo
