|
From: Julian S. <js...@ac...> - 2006-08-25 10:13:15
|
---------- Forwarded Message ---------- Subject: Re: FYI: Valgrind 3.2 port to FreeBSD Date: Friday 18 August 2006 10:41 From: Julian Seward <js...@ac...> To: Peter Wemm <pe...@we...> Cc: Nicholas Nethercote <nj...@cs...> On Tuesday 15 August 2006 22:59, Peter Wemm wrote: > Progress update: Cool! > up in the last email yet. But I thought a FYI might be in order. Indeed; good to see progress. > My most recent "problem" was aspacemgr.c:get_name_from_fd() and > resolve_filename() in m_libcfile.c. We have no /proc/self/fd/<nn> > or equivalent. I didn't want to deal with adding code to track names > associated with fd's so I cheated and used a kernel module to extract > the current pathnames. It is a hack of the worst kind, but I don't > want to deal with it right now. I think we might add the > functionality to FreeBSD and use the kernel modules for older releases. Do you need to know these names? What happens if you just produce fake strings with no useful info? I'm moderately sure m_aspacemgr doesn't really care what files are called - that's just for being pretty for the user's benefit. > BTW: the above traces appear to be real. valgrind 2.2 also complains > about the same problem, in spite of the protests from the author of the > code in question that it isn't possible... There are various classes of false errors that tend to happen, especially in libcs, and especially when bringing the system up on new platforms. Let me know if you want help chasing this down. J ------------------------------------------------------- |