As some of you might be aware, recently I've been working on porting the excellent valgrind debugger to FreeBSD (both -stable and -current). If you are interested in trying it out, you can find details on how to get the latest version at http://www.rabson.org/#valgrind. Enjoy...
Doug Rabson wrote:> As some of you might be aware, recently I've been working on porting the > excellent valgrind debugger to FreeBSD (both -stable and -current). If > you are interested in trying it out, you can find details on how to get > the latest version at http://www.rabson.org/#valgrind. Enjoy...I've successfully tried the following valgrind tarball (actually, part of a DragonFLY port), which made out of your patches. It compiles on 5.x systems perfectly, and actually runs quite well (procfs is required though, to eliminate SIGBUS). http://eirikn.kerneled.com/valgrind/ -- Lev Walkin vlm@netli.com
Doug Rabson wrote:> As some of you might be aware, recently I've been working on porting the > excellent valgrind debugger to FreeBSD (both -stable and -current). If > you are interested in trying it out, you can find details on how to get > the latest version at http://www.rabson.org/#valgrind. Enjoy...This page refers to svn://svn.rabson.org/repos/valgrind/branches/stable but Mozilla apparently doesn't know what svn means (nor do I), and can't retrieve it. I tried changing it to http to no avail. Sorry if I'm being dense, but what is that, and how do I get to it? Thanks Joe
Doug Rabson wrote:> As some of you might be aware, recently I've been working on porting the > excellent valgrind debugger to FreeBSD (both -stable and -current). If > you are interested in trying it out, you can find details on how to get > the latest version at http://www.rabson.org/#valgrind. Enjoy...This page refers to svn://svn.rabson.org/repos/valgrind/branches/stable but Mozilla apparently doesn't know what svn means (nor do I), and can't retrieve it. I tried changing it to http to no avail. The examples in the web page refer to something called svn, but I don't seem to have that on my system or in the ports tree. Sorry if I'm being dense, but what is that, and how do I get to it? Thanks Joe
On Apr 9, 2004, at 7:07 AM, Doug Rabson wrote:> As some of you might be aware, recently I've been working on porting > the > excellent valgrind debugger to FreeBSD (both -stable and -current). If > you are interested in trying it out, you can find details on how to get > the latest version at http://www.rabson.org/#valgrind. Enjoy...For anyone trying to build on FreeBSD 5.1, it requires a small tweak, since libc_r in that version did not have support for pthread_spinlock_t's. I believe this is the correct change, since __FreeBSD_version 501107 seems to be the next bump after the addition of pthread_spinlock_t support. -garrett Index: coregrind/arch/x86-freebsd/vg_libpthread.c ==================================================================--- coregrind/arch/x86-freebsd/vg_libpthread.c (revision 325) +++ coregrind/arch/x86-freebsd/vg_libpthread.c (working copy) @@ -2774,7 +2774,7 @@ /* POSIX spinlocks, taken from glibc linuxthreads/sysdeps/i386 */ -#if __FreeBSD__ == 5 +#if __FreeBSD_version >= 501107 int pthread_spin_init(pthread_spinlock_t *lockp, int pshared) { struct pthread_spinlock *lock = my_malloc(sizeof(struct pthread_spinlock));
Doug Rabson wrote:> As some of you might be aware, recently I've been working on porting the > excellent valgrind debugger to FreeBSD (both -stable and -current). If > you are interested in trying it out, you can find details on how to get > the latest version at http://www.rabson.org/#valgrind. Enjoy...I'm a little confused at some of the results I see. I'm trying to use valgrind as part of the daily build tests for the curl project. The tests work fine on linux, but with the FreeBSD version of valgrind I get this fbsd$ valgrind --leak-check=yes --logfile-fd=3 src/curl/usr/libexec/ld-elf.so.1: Cannot open "/usr/local/lib/valgrind/vg_inject.so" fbsd$ ls -l /usr/local/lib/valgrind/vg_inject.so -rwxr-xr-x 1 root wheel 38445 Apr 12 09:26 /usr/local/lib/valgrind/vg_inject.so* fbsd$ file /usr/local/lib/valgrind/vg_inject.so /usr/local/lib/valgrind/vg_inject.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped However, it seems to work ok if I don't use --logfile-fd=3. Unfortunatly I don't have the time or the expertise to go through the code at the moment, so I'm hoping this might suggest something to you. Thanks Joe
Doug Rabson wrote:> As some of you might be aware, recently I've been working on porting the > excellent valgrind debugger to FreeBSD (both -stable and -current). If > you are interested in trying it out, you can find details on how to get > the latest version at http://www.rabson.org/#valgrind. Enjoy...After consultation with Doug Rabson, I have created ports for valgrind (stable version and a more ``bleeding edge'' development version). Until they hit the tree (probably after the ports freeze), you can get them at: http://home.leo.org/~barner/freebsd/valgrind/ Happy bug hunting, Simon -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: Digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040423/47dc1be8/attachment.bin
On Sun, Apr 25, 2004 at 15:01:03 EDT, David O'Brien scribbled these curious markings:> [*] And I would like to see a lot more of these, as I generally use > Kris's packages vs. building from ports and I end up with a lot morecrap> on my system than I need.Yuck. I don't want to have to install _two_ packages for a library to be able to build software with it. If I wanted that, I'd use Linux. ... Well, maybe not. Perhaps a port Makefile hook, a la NOPORTDOCS, could be used? Of course, the snag there is deciding which camp to please insofar as default settings are concerned. It'd be cool if you could put your decision in /etc/make.conf and have it global, so you can just forget about it and live your life as you want. =) -- I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Unix is user friendly. However, it isn't idiot friendly. - Please CC me in all replies, even if I'm on the relevant list(s). -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040425/24104970/attachment.bin