Date: Sat, 8 Oct 2011 12:42:02 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= <romain@FreeBSD.org> To: Omer Faruk SEN <omerfsen@gmail.com> Cc: mdf@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Using Valgrind on FreeBSD Message-ID: <20111008104202.GA9473@FreeBSD.org> In-Reply-To: <CAG%2Br6L9S2y1uBtd5hL_p4JXA9UBw1kNK_rBroZ2s7VyR7jQ_ng@mail.gmail.com> References: <4E8F400D.80305@gmail.com> <CAMBSHm-hPSV0XGL2MiZAATEOPxg7_vSGdPNUCATiqcxnAE8C8A@mail.gmail.com> <CAG%2Br6L9S2y1uBtd5hL_p4JXA9UBw1kNK_rBroZ2s7VyR7jQ_ng@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! On Sat, Oct 08, 2011 at 09:57:44AM +0300, Omer Faruk SEN wrote: > May it be related with the patches for Valgrind that > http://people.freebsd.org/~romain/valgrind/ written? It may require to > rebuild valgrind with that patch but I am not sure. Maybe Romain can answ= er > that question. Long story short: I wrote some code I wanted to test with Valgrind and got the message saying that some syscall wrappers where not available. Since the IPC stuff was quite trivial and my concerns where about another part of the code, I started hacking these system calls in order to avoid Valgrind quitting when they where called so that it could check the 'important' part of my code. Then, I wondered how hard it would have been to make a complete IPC syscalls support for FreeBSD in Valgrind, unfortunately I could not get much time to take on this and I decided to push my patches 'as it' at some location I could get them back is necessary. =2E.. and it looks like Google indexed it. Basically, the code is copy-pasta with minor tweaks of other parts of Valgrind. It is NOT production-ready. It does not build because I pushed it after trying to add support for all message queues and semaphores syscalls after testing my program with the 2-3 system calls that where missing for it to run. I took a few minutes to fix the build (at least on 8-STABLE amd64, new patches are here: http://people.freebsd.org/~romain/valgrind/2011-10-08/ ) but I have not even tried to test anything, so beware! To use these patches, create a 'files' directory in the Valgrind port and put them there, then install the port as usual. If you would like to work on expanding IPC support in Valgrind on FreeBSD, please write me a line. Maybe we can coordinate some work ;-) Thanks! Romain --=20 Romain Tarti=E8re <romain@FreeBSD.org> http://people.FreeBSD.org/~romain/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQGcBAEBAgAGBQJOkCj4AAoJELpNHZVREjNvWxgL/0hq4rsNWLjFDM962EmyLaqy d5qXRBcgvm28Zb9i+gUC+evLwrltNDJ3r1lVxmm0NEGbG47FTRsL9wzluGC4Ix/Q MUUveWXe4MKc2I26YZKdKRcNzXMpaZztErrGaolu8lXOu7t3lWUg85Wz8Xi28tEz HQsFya3HV85OKjzAgwCTrEFHaMxEpVLkMRT9k/ihfKu7sjZyIj4ui975KvdKCrBl VVjHDE1b4FujKCtGGv+xQLDLDmQJWzf9bBUcdgijLcx6tjLQo9JIhRwn1OSBlMje nfWKKE/3bXOKYiaNQXbZNGmtYgxn6hfo4DyNexp1q3SZgvwIb3s+9hQwZEov1+21 cTIp/oJipoXP6Djm/m9o82rJi1YMC4HITQphyYfM/ipMq2kverxnC2ui2DmhT5ix N7U7AOuKTPSOFrP+In1eC8Cc0Ggoz3YB0gFaOh2qax45q3iY1AFzjDJMC+LtWBNN rZ31xjvds4HA+qvewod6d+CvzdUvwqw/7t6iRuA0RA== =M7rS -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111008104202.GA9473>