summaryrefslogtreecommitdiff
path: root/dvb-spec/README.valgrind
diff options
context:
space:
mode:
authorholger <devnull@localhost>2002-10-10 16:22:27 -0300
committerholger <devnull@localhost>2002-10-10 16:22:27 -0300
commit5a523e605b9b6d1ae50d0707c1874c5b7f0959cc (patch)
tree4dfe1bf1f9ae2f2eefb5d34a42cc4ba029817091 /dvb-spec/README.valgrind
parentab85b007da42f42856a775d8cff97332093f5b34 (diff)
downloadmediapointer-dvb-s2-5a523e605b9b6d1ae50d0707c1874c5b7f0959cc.tar.gz
mediapointer-dvb-s2-5a523e605b9b6d1ae50d0707c1874c5b7f0959cc.tar.bz2
the new HEAD
Diffstat (limited to 'dvb-spec/README.valgrind')
-rw-r--r--dvb-spec/README.valgrind13
1 files changed, 13 insertions, 0 deletions
diff --git a/dvb-spec/README.valgrind b/dvb-spec/README.valgrind
new file mode 100644
index 000000000..c1ce7c994
--- /dev/null
+++ b/dvb-spec/README.valgrind
@@ -0,0 +1,13 @@
+valgrind-1.0pre3-dvb.patch enables checking correct usage
+of the the Linux DVB API ioctls with valgrind
+(http://developer.kde.org/~sewardj/). Or, more to the point,
+it allows you to check your DVB software with valgrind
+without getting all those "unknown ioctl" warnings.
+
+Notes:
+- only frontend and demux ioctls are currently implemented
+- some ioctls take structs as arguments; due to padding, valgrind
+ will complain about uninitialized data passed to the ioctl unless
+ you memset() the whole struct to some defined value
+
+Johannes Stezenbach <js@convergence.de>