Hi,
I have used below program for testing. Below are the steps I have followed.
Compile: gcc -g3 test_shm.c -o test_shm
Create shared memory: ./test_shm –c
Get shared memory without valgrind: ./test_shm –g ( this works fine)
Get with valgrind: /usr/bin/valgrind --tool=memcheck
The code was mangled by posting in HTML. Instead, use plain text (or an
attachment,
if the mailing list allows them.) I [attempt to] attach the code I used:
-rw-rw-r--. 1 jreiser jreiser 3125 Aug 14 09:30 shmtest.c
On my system, /usr/include/linux/shm.h says:
-
#define SHMMAX 0x200
On 13/08/2012 2:54 PM, Julian Seward wrote:
Hi Christoph,
Thanks for the update. It's great to hear this is being worked on.
Hi Julian, nice to hear from you. I've been working on this project for
about a year now, and I am 100% sure that there can be a working
Valgrind for Windows one day.
I want to signal a pthread condition variable without holding the
associated mutex. DRD (correctly) flags this as an error, but I want
to suppress the error. I'd like to do it with a client request like
DRD_IGNORE_VAR. I tried putting this on the cond and the mutex, and
the error is still
On Tuesday, August 14, 2012, Leif Walsh wrote:
I want to signal a pthread condition variable without holding the
associated mutex.
Hmm, you really really want to do that and 110% understand the possible
races that could result? I looked at a situation like this in NSPR some
time back and found
On Tue, Aug 14, 2012 at 2:55 PM, Julian Seward jsew...@acm.org wrote:
Hmm, you really really want to do that and 110% understand the possible
races that could result?
Yep, I really do want to do that. I really do not care about the
race. I suppose I could switch to a semaphore or something
On Tuesday, August 14, 2012, Leif Walsh wrote:
because there are lots of different stacks that trigger this, and the
optimizer, especially with -flto, messes with the function names in a
different way each time we build.
Does it mess with the names so much that you can't use the * and ?
This may work, I forgot you could use wildcards in function names.
I'll come back if it doesn't.
On Tue, Aug 14, 2012 at 3:46 PM, Julian Seward jsew...@acm.org wrote:
On Tuesday, August 14, 2012, Leif Walsh wrote:
because there are lots of different stacks that trigger this, and the
optimizer,
On Tue, 2012-08-14 at 10:20 +, Adishesh wrote:
Hi,
I have used below program for testing. Below are the steps I have
followed.
Compile: gcc -g3 test_shm.c -o test_shm
Create shared memory: ./test_shm –c
Get shared memory without valgrind: ./test_shm –g ( this works fine)
Get with
