Odd resource overstep problem

[cmouse]

grsec: From 62.237.194.186: (default:D:/usr/bin/valgrind) attempted resource overstep by requesting 196608 for RLIMIT_DATA against limit 0 by /usr/bin/valgrind[valgrind:25529] uid/euid:1000/1000 gid/egid:1000/1000, parent /bin/bash[bash:5686] uid/euid:1000/1000 gid/egid:1000/1000

$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 100
virtual memory (kbytes, -v) unlimited

subject /usr/bin/valgrind
RES_DATA 1M 1M

Why does it claim that my RLIMIT_DATA is 0 even when it isn't?

[spender]

valgrind for some reason is setting its RLIMIT_DATA to 0. You can see it using setrlimit if you strace it. I don't know why it's doing that though.

-Brad