[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] database trouble
From: |
Jim Segrave |
Subject: |
Re: [Bug-gnubg] database trouble |
Date: |
Tue, 8 Oct 2002 14:58:33 +0200 |
User-agent: |
Mutt/1.4i |
This time getting the mailing list address right:
On Tue 08 Oct 2002 (14:50 +0200), Gamma wrote:
> Thank you for your reply Jim,
> yes in fact I have MS Windows as operative system and I thought that the
> address bug-gnubg is just for the windows version....
> Anyway I'm sad because I can't use this useful function and I don't know who
> to ask...
> Greetings
> GM
We need to get someone else with a Window's build environment to try
this and see if they can reporduce the problem. There are several
readers of the bug-gnubg mailing list who definitely do have
Windows. I don't know what tools are available for debugging the
problem once it's found.
> ----- Original Message -----
> From: "Jim Segrave" <address@hidden>
> To: "Gamma" <address@hidden>
> Cc: <address@hidden>
> Sent: Tuesday, October 08, 2002 10:56 AM
> Subject: Re: [Bug-gnubg] database trouble
>
>
> > On Tue 08 Oct 2002 (05:47 +0200), Gamma wrote:
> > > Dear GNU,
> > >
> > > I have a message error "gnubg.gdbm: Can't be writer" when I try to
> generate/rollout/import database and if I try to dump/export or train from a
> database the message error shown is that the file gnubg.gdbm is empty. Why?
> >
> >
> > The error message comes from the gdbm database library. It occurs when
> > you try to open the database file for writing. The library attempts to
> > lock the file and, if that fails, you will get this message.
> >
> > I am guessing from your email that you are running gnubg on
> > Windows. If that's the case, I can't really give you much more
> > information, as I know nothing about the Windows port of the gdbm
> > software nor how Windows handles file locking.
> >
> > --
> > Jim Segrave address@hidden
>
--
Jim Segrave address@hidden
----- End forwarded message -----
--
Jim Segrave address@hidden