On Fri, Sep 05, 2008 at 08:42:05AM +0000, Clint Adams wrote:
> On Wed, Sep 03, 2008 at 10:13:36PM -0700, Steve Langasek wrote:
> > But figuring out where this EINVAL originates seems to be non-trivial.
> Suggestion from Oracle:
> | Please configure an error stream, with DB_ENV->set_errfile. That should
> | indicate the cause of the error. If the named database file already
> | exists, but the format doesn't match (e.g., it is not encrypted, or not
> | a btree database), then you would get this error.
Well, obviously it's not any of these errors since this is their own test
suite... but done anyway, to see what kind of output we get:
FILE *errfile;
errfile = fopen("/home/vorlon/debugging-db.log", "w");
i = db_env_create(&env, 0);
i = env->set_encrypt(env, "passw0rd", DB_ENCRYPT_AES);
i = env->set_errfile(env, errfile);
[...]
/home/vorlon/debugging-db.log is created as an empty file.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
