> I think I give up on this. With another user, we've been able > to identify > where the infinite loop is, and it is a condition that should > never happen > if the database is not corrupted. The GDBM bug list (and > google) does not > show any sign of such reports, and GDBM is pretty heavily > used in the Unix > world. No, the database size is not a problem, since I use it > in other > projects with DB up to several hundreds MB. OTOH the Win32 "port" is > really nothing, since the GDBM code uses almost completely POSIX > functions. There must be something in the code generation (MS > VC++?) that > trigger the condition, or the GLST processes gets brutally > killed while > updating the DB files. > > > > - Davide > >
I don't say it is directly related to gdbm database size or library but problems I had come up only then the database size is bigger than 10Mbytes .... You said it could be a VC++ generated code problem. Is it possible to have a gcc/win32 (in mind with mingw32) compiled version for win32 ? (or give me directions to compile with gcc for win32 ...) Thanks Francis - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
