Re: [Valgrind-users] Debugging a GC with valgrind

2011-01-21 Thread WAROQUIERS Philippe
8 #define RZ_SZB (128) char *sp = /* stack pointer value */; char vbits[RZ_SZB] = {0}; VALGRIND_GET_VBITS(sp-RZ_SZB, vbits, RZ_SZB); VALGRIND_MAKE_MEM_DEFINED(sp-RZ_SZB, RZ_SZB); /* ... scan the red zone here ... */ VALGRIND_SET_VBITS(sp-RZ_SZB, vbits, RZ_SZB); 8 I can

[Valgrind-users] AIX 5.3 - Valgrind 3.3.1

2011-01-21 Thread Stutz Oliver
There is not much in the Net about AIX-Valgrind but i have found posts from people who claim that 3.3.0/1 runs. The ./configure works Properly for me... but here i get stuck, the question is why is that, i have no clue what the -C stands for otherwise i could eventually replace it.

Re: [Valgrind-users] AIX 5.3 - Valgrind 3.3.1

2011-01-21 Thread Stutz Oliver
I'am now using Gmake, i can compile the memchecker with the hack: http://unix.derkeiler.com/Newsgroups/comp.unix.aix/2004-11/0553.html unfortunately it will only make it compile and coredump if i start it. Has anybody a clue what my real issue is here? I have added the -lcrypt flag and

Re: [Valgrind-users] AIX 5.3 - Valgrind 3.3.1

2011-01-21 Thread Oliver Schneider
On 2011-01-21 08:59, Stutz Oliver wrote: There is not much in the Net about AIX-Valgrind but i have found posts from people who claim that 3.3.0/1 runs. The ./configure works Properly for me... but here i get stuck, the question is why is that, i have no clue what the -C stands for

[Valgrind-users] Fwd: Re: AIX 5.3 - Valgrind 3.3.1

2011-01-21 Thread Stutz Oliver
I have now added the -lcrypt flag and it actually can resolve the symbols found in libc.a The Problem is that Valgrind Coredumps immediately after start with sig 4 Has nobody a Static Linked Valgrind for AIX 5.3? We also used OBJECT_MODE=64 and the other time with 32 The 64 bit version

Re: [Valgrind-users] AIX 5.3 - Valgrind 3.3.1

2011-01-21 Thread Julian Seward
IIRC, you need to be running a 64-bit kernel. V will segfault on AIX if you're running a 32-bit kernel. Also I thought 3.4.1 worked on AIX5.3. It's generally better than 3.3.1, if only because then you'll have origin tracking for Memcheck. J On Friday, January 21, 2011, Stutz Oliver wrote:

Re: [Valgrind-users] Debugging a GC with valgrind

2011-01-21 Thread Dave Goodell
On Jan 20, 2011, at 6:43 PM CST, john skaller wrote: OK, so I do this now: ... if(debug) fprintf(stderr, Check if *%p=%p is a pointer\n,i,*(void**)i); scan_object(*(void**)i, reclimit); ... The VALGRIND macro there doesn't seem to be working, I must be doing

Re: [Valgrind-users] Debugging a GC with valgrind

2011-01-21 Thread john skaller
On 22/01/2011, at 2:30 AM, Dave Goodell wrote: On Jan 20, 2011, at 6:43 PM CST, john skaller wrote: OK, so I do this now: ... if(debug) fprintf(stderr, Check if *%p=%p is a pointer\n,i,*(void**)i); scan_object(*(void**)i, reclimit); ... The VALGRIND macro there