41,895 lines (1.5MB)<\/strong>.\u00a0 But note that this is not a very useful metric;\u00a0 progress will usually cause it to drop, but it will also increase as missing Darwin functionality is added.<\/li>\n<\/ul>\nInterestingly enough, although this number of Mac test failures has gone down significantly, if the branch didn’t handle your program a month ago it probably still won’t handle it now (although getsockopt() no longer causes an abort).\u00a0 But Valgrind’s output may well be better (e.g. debugging information will be better utilized).\u00a0 Much of my effort has been in making the tests pass — improving cases where the Darwin port was doing basically the right thing, but its output didn’t exactly match that expected.<\/p>\n
One example is that stack traces were a little unclean, in various minor ways.\u00a0 Another example is that I added a –ignore-fn option to Massif (the heap profiler) which allows it to ignore certain heap allocations.\u00a0 This was required because Darwin’s libc always does a few heap allocations at start-up, but Linux’s libc doesn’t.\u00a0 The new option allows the Darwin allocations to be ignored and therefore Massif’s output to be consistent on both platforms.<\/p>\n
Few if any of these changes have made the branch closer to handling new programs, at least directly.\u00a0 But there’s no point apologising about this, because the branch won’t reach a highly functional state without a working test suite to serve as a safety net against regressions.\u00a0 And as I progress, getting more tests to pass will require genuine new program functionality to be supported, so improvements should start to occur on that front soon.\u00a0 For example, signals currently aren’t supported at all, and this is why Firefox does not run under Valgrind on Mac yet — all calls to sigaction() currently return -1, which causes an assertion failure somewhere in NSPR.<\/p>\n
Something else worth mentioning:\u00a0 I bought a new MacBook Pro, as my old 32-bit only was was slow and noisy and getting annoying.\u00a0 The new machine is 64-bit capable, but compiles to 32-bit by default and Valgrind’s configure script identifies it as a 32-bit only machine.\u00a0 If anybody knows how to make configure recognise that it’s a 64-bit machine I’d love to hear about it.<\/p>\n
Update, March 17:<\/strong> fixed a broken link to an earlier post.<\/p>\n","protected":false},"excerpt":{"rendered":"It’s been a month since I first wrote about my work on the Mac OS X port of Valgrind.\u00a0 In that time I’ve made 85 commits to the DARWIN branch (and a similar number to the trunk). Here are the current (as of r9192) values of the metrics I defined in the first post as […]<\/p>\n","protected":false},"author":139,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[487,484],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/16"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/users\/139"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/comments?post=16"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/16\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/media?parent=16"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/categories?post=16"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/tags?post=16"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}