|
From: David J. K. <dke...@ko...> - 2002-07-24 12:23:13
|
Install VFSHelper build 738 (I'm mailing it to you off-list), reproduce the
error, and give me the new line #
What I *really* need is a consistantly reproducable test case. Running with
the logging version of VFSHelper can slow things down by as much as 1000%
and generates so much data that you can't just run normally with it and wait
for the problem to pop up.
If I had to guess, I'd say it's a memory management problem in FileCaddy. If
you reproduce it with build 736 we should be able to pin it down to a
particular VFS call and that may tell us where to go look.
--
- Dave Kessler
President - Kopsis, Inc.
http://kopsisengineering.com
On Tue, Jul 23, 2002 at 01:03:39PM -0700, Matthew Bevan wrote:
> In reference to:
> http://sourceforge.net/tracker/index.php?func=detail&aid=583896&group_id=56482&atid=480741
>
> This really, really, needs to be fixed.
>
> Dave, you're the master of VFSMgr, what's your take on this?
> ../Src/VFSMgr.c, Line: 3386
> FATOpenFile: 0x2A08
>
> It seems to happen semi-randomly when copying files (doesn't seem to
> matter the size of individual, the group, the number of files, etc.)
>
> --
> Matthew (Darkstorm) Bevan mb...@ma...
> Margin Software, NECTI. http://www.marginsoftware.com
> Re-inventing the wheel, every time.
>
> - A closed mouth gathers no foot.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Filecaddy-developers mailing list
> Fil...@li...
> https://lists.sourceforge.net/lists/listinfo/filecaddy-developers
|