On Thu, Mar 14, 2013 at 06:30:43PM +0100, Alessandro Ghedini wrote: > I'll have a look as soon as I have some free time. I was also thinking that > the > patch may be applied only in the kfreebsd builds, so it wouldn't interfere > with > the linux builds.
That sounds great, but I do not yet have the debian expertise to know how to express this in debian/rules (or whereever the appropriate location is) > What did you do to see if the build actually works? I ran some very simple (certainly by comparison to iceweasel or libreoffice), non-interactive programs of my own. > A simple > stress-test for the MemCheck tool would be to run it on firefox/iceaweasel and > libreoffice and see what happens. Unfortunately, firefox doesn't work, possibly due to an unimplemented syscall. --51670-- WARNING: unhandled syscall: 330 --51670-- You may be able to write your own handler. --51670-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --51670-- Nevertheless we consider this a bug. Please report --51670-- it at http://valgrind.org/support/bug_reports.html. this is apparently SYS_sched_getscheduler, so its dear neighbor SYS_sched_setscheduler will probably also need implementation. I'll try to devote some time to this item this weekend. > Also, does it work on kfreebsd-i386 too? I have not tested this. I suspect it at least has the sysarch(I386_SET_GSBASE) problem in addition to any problems in the amd64 build. I don't have a kfreebsd-i386 installation at the moment, and due to some compile-time bug I encountered, the kfreebsd-amd64 build is 64bitonly. > Anyway, as I mentioned on the debian-bsd list the real problem here is not > really the patch itself, but finding someone willing to maintain it in the > future (at least until it gets merged upstream) since I'm not qualified (nor > really interested) in the kfreebsd ports. So would you be willing to continue > to maintain the patch in the future? If so you are welcome to push your > changes > to the collab-maint git repository where valgrind is maintained [0] in a > separate branch called, say, "kfreebsd" (possibily without the d/changelog > changes). I have some level of committment to doing software development on debian-kfreebsd, and I find valgrind to be a useful tool. That being the case I have some stake in whether it works or not. I'm not yet a DD so I can't yet do things like push branches onto anonscm.debian.org, but it's becoming clear that I should go ahead and become one. I assume that for the moment it's appropriate to attach any updated patches to this bug report. If that's inappropriate, please let me know. Thanks, Jeff -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org