|
From: Szakacsits S. <sz...@si...> - 2003-12-23 08:01:33
|
On Tue, 23 Dec 2003, Jan Kratochvil wrote: > I have suspection libntfs is leaking memory. It's possible. I've found there were ususally 1-3 bugs in the libntfs functions I used. This is expectable because, as I was explained, Anton doesn't verify/test the code he writes. Please see more here for example, http://marc.theaimsgroup.com/?l=linux-ntfs-dev&m=104626284218891&w=2 I revise functions/patches when I use them moreover use electric fence, valgrind and automatic testing to catch new errors. > I did not yet investigate it much Sorry but I don't have time either, in one hour I'm more or less away from computers for a week. If you don't get answers (linux-ntfs-dev became moderated due to spams and sometimes it takes 3+ days to approve a message) I'm afraid you have to look at it yourself. I'm also close to finish ntfsresize with unlimited relocation support (Miguel Lastra and Dewey M. Sasser helped a lot to achieve this) and I need a very important fix to be applied to libntfs but I didn't get response so far for my patches whereever I send them (since the cvs->bk change I can't commit). The other solution you might have is by looking for the driver this way: - read /boot.ini - get the system directory from boot.ini (e.g. /winnt) - get the drivers from system_directory/system32/drivers (I don't know if other places are also possible) Merry Christmas :) Szaka |
