On 6/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
In the Makefile, "CFLAGS = -g -O2", so it looks like debugging
is turned on. However, when I type "gdb gnubg" and then type
"run --sync", after the crash I get:
Program exited with code 01.
(gdb) backtrace
No stack.
=
Ye
I have not tried it in the 2D version, but I suspect that it will
work fine. Apparently, it is an X11 thing. My system is Redhat
Enterprise Linux 5 with all of the latest patches. I did upgrade
the ATI graphics driver because the default driver was horribly
slow. My system is a Dell Precision
This bug looks awfully like the one that plagued the X-Windows builds on
OS/X (With X11).
Does this happen if you run the 2d version? I'm also curious what OS?
On 6/21/07 2:25 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> In the Makefile, "CFLAGS = -g -O2", so it looks like debugging
> i
In the Makefile, "CFLAGS = -g -O2", so it looks like debugging
is turned on. However, when I type "gdb gnubg" and then type
"run --sync", after the crash I get:
The program 'gnubg' received an X Window System error.
This probably reflects a bug in the program.
The error was 'Bad
Hi Øystein,
Yes!
I think we should view the Computer Olympiad as a tournament (as it's
actually is), and not as an analysis of which program is best.
Total agreement agree.
Do I read between the lines that you have matched the two against each
other? What's the score?
S4, JF, GnuBG 0.15,
> From: Christian Anthon
>
> I would be glad and honored to have the medal, but my vote
> goes to the ones that did the actual work as well. I really
> appreciate that someone takes the time to do this kind of
> thing. Even though it seems that we do more to promote
> BGBlitz than anything els
I would be glad and honored to have the medal, but my vote goes to the
ones that did the actual work as well. I really appreciate that
someone takes the time to do this kind of thing. Even though it seems
that we do more to promote BGBlitz than anything else.
Christian.
On 6/18/07, Adrian Wright
Hi Øystein,
when you say benchmark does that mean just that or have the positions
been used for training in some way? And why are the positions in there
in the first place (0 and 2ply disagrees or something)? I'm a big fan
of being systematic, so taking out positions that you don't like is
not my
This is what I would do to track the bug down:
1) Install the debug info packages for glibc, glib and gtk and X.
2) Install the gnu debugger (gdb)
3) Make sure that the -g (or -ggdb) is turned on while compiling gnubg.
4) make install
5) run the following command 'gdb gnubg' (assuming /usr/local/
