Re: [Bug-gnubg] New Win distrib and exes (20090127)

[Massimiliano Maini]

Hi N.,

what Christian is suggesting would be
my best guess too, since I tried a few (short) 
rollouts and it works fine for me.
Double check with dependency walker
(http://www.dependencywalker.com/) that
your gnubg.exe is only using dlls from
its own directory (except system stuff).
In particular, check that its not using
any gtk stuff from your own dir.

If my memory is not wrong, this happened
in the past and the reason was a dll mismatch.

MaX.

Christian Anthon <address@hidden>
wrote on 27/01/2009 22:41:29:

> I don't want to boot in windows right now, so my best guess would
be
> that you have dll's linked from outside the gnubg dir. There are tools
> to look at that kind of thing, try googling dll walker.
> 
> Christian.
> 
> On Tue, Jan 27, 2009 at 7:32 PM, motiv4u <address@hidden>
wrote:
> >>
> >>> This 20090127-build gives me several "-1.#QO"
as soon as I do a
> >>> roll-out (in stead of the normal 0,xxxx or 0.xxxs)
> >>> The same -1.#QO does not show in the Windows build following
the steps
> >>> in Jon's "Building gnubg on MS Windows" ( URL:
> >>> http://www.gnubg.org/index.php?itemid=50 ) nor on the
Ubuntu builds.
> >>>
> >>> N.
> >>
> >> Hmm strange. I trie a simple rollout and worked fine for
me. Can you
> >> send me the exact case to reproduce (position/match ID, moves
to rollout,
> >> rollout settings) ?
> >
> > Whatever position, whatever match or money... all result in -1.#QO
in
> > stead of the equities. Just get a Hint, select a couple of moves
(free
> > choice) and let the rollout start. You'll get them (at least:
I get
> > them always)
> >
> > Is it possible the snapshot you're using is an "in between"
situation?
> > While someone was doing an update of the CVS? Just my 2,5 cents.
> > N.
> >>
> >> Thx,
> >>
> >> MaX.
> >
> >
> > _______________________________________________
> > Bug-gnubg mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/bug-gnubg
> >