[Valgrind-developers] 2007-12-24 03:15:03 GMT nightly build (alvis, i686, Red Hat 7.3)

2007-12-23 Thread Tom Hughes
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-12-24 03:15:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ..

[Valgrind-developers] 2007-12-24 03:05:08 GMT nightly build (lloyd, x86_64, Fedora 7)

2007-12-23 Thread Tom Hughes
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2007-12-24 03:05:08 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ...

[Valgrind-developers] 2007-12-24 03:10:03 GMT nightly build (dellow, x86_64, Fedora 8)

2007-12-23 Thread Tom Hughes
Nightly build on dellow ( x86_64, Fedora 8 ) started at 2007-12-24 03:10:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ..

[Valgrind-developers] 2007-12-24 03:00:03 GMT nightly build (gill, x86_64, Fedora Core 2)

2007-12-23 Thread Tom Hughes
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-12-24 03:00:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests

Re: [Valgrind-developers] exp-drd crash

2007-12-23 Thread Julian Seward
> #0 vgPlain_get_StackTrace2 (tid_if_known=, > ips=0x389113f0, n_ips=12, ip=0, sp=0, fp=0, lr=0, fp_min=0, > fp_max_orig=0) at m_stacktrace.c:230 The stack unwinder is being started with ip, sp, fp, lr values for the thread concerned of zero, which leads to the segfault. Are you sure the thr

Re: [Valgrind-developers] Valgrind and Wine

2007-12-23 Thread Tom Hughes
On 23/12/2007, Eric Pouech <[EMAIL PROTECTED]> wrote: > Tom Hughes a écrit : > > In message <[EMAIL PROTECTED]> > > Tom Hughes <[EMAIL PROTECTED]> wrote: > > > >> I have recently been working on trying to get valgrind and wine to > >> work together and have run into a rather nasty problem.

Re: [Valgrind-developers] exp-drd crash

2007-12-23 Thread Bart Van Assche
Update: the patch included below solves the exp-drd crash. This patch backs out the post-3.3.0 changes in coregrind/m_stacktrace.c. Index: coregrind/m_stacktrace.c === --- coregrind/m_stacktrace.c(revision 7307) +++ coregrind/m_st

[Valgrind-developers] New script: debug-in-place

2007-12-23 Thread Bart Van Assche
A convenient tool for running Valgrind without installing it is the vg-in-place script. I have written a similar script that sets up the proper environment variables for debugging a tool. Can this script please be reviewed and applied if it is considered acceptable ? Note: the script has not yet be

[Valgrind-developers] exp-drd crash

2007-12-23 Thread Bart Van Assche
Since a few days exp-drd now crashes on every program that I try to analyze. This crash did not yet occur with Valgrind version 3.3.0 but does occur with revision 7307. The relevant call stack is shown below. Is this due to exp-drd or due to the post-3.3.0 changes ? $ ./debug-in-place --tool=exp-d

Re: [Valgrind-developers] Valgrind and Wine

2007-12-23 Thread Eric Pouech
Tom Hughes a écrit : > In message <[EMAIL PROTECTED]> > Tom Hughes <[EMAIL PROTECTED]> wrote: > > >> I have recently been working on trying to get valgrind and wine to >> work together and have run into a rather nasty problem. >> > > Unprelinking libwine has temporarily got me past