Ticket #149 (Fixed)Sat Sep 08 23:07:18 UTC 2007
Use of !MemCheck
| Reported by: | Rob F Johnson (156) | Severity: | Normal |
| Part: | Legacy: Batch 1 issues | Release: | |
| Milestone: | Status | Fixed |
Details by Rob F Johnson (156):
Four BatchOne components in Networking.Fetchers (Finger, Generic, Gopher and WhoIs) call for DrSmith’s !MemCheck in sources module and start. The compilations fail because I don’t have it.
A fifth component FTP also looks for !MemCheck in the same places, but the compilations work because it first tests for the presence of variable MemCheck_MEMCHECK. I presume this variable is set by DrSmith’s software.
Is MemCheck a testing option that isn’t needed in the final object? Can it be made optional in the other four components?
Changelog:
Modified by Steve Revill (20) Sat, September 22 2007 - 20:52:55 GMT
- Status changed from Open to Fixed
Oops. This was missed in our testing because the build machine had Dr Smiths on it (in another build) so the components built fine for us. I’ve now fixed the four problem components so you shouldn’t have this issue now.
Modified by Rob F Johnson (156) Mon, October 22 2007 - 10:18:43 GMT
- Status changed from Fixed to Open
I downloaded the updated version of Batch One and rebuilt the 4 affected components. I think you’ve missed 1 line that needed ‘suppressing’.
Networking.Fetchers.Generic.c.start still has a naked reference to MemCheck_UnRegisterMiscBlock on line 112.
Modified by Steve Revill (20) Fri, April 24 2009 - 02:03:13 GMT
- Status changed from Open to Fixed
Fixed in the latest commit to cvs.
