[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] Bug: segfaults during longer rollouts
From: |
Jim Segrave |
Subject: |
Re: [Bug-gnubg] Bug: segfaults during longer rollouts |
Date: |
Thu, 26 Jun 2003 22:25:19 +0200 |
User-agent: |
Mutt/1.2.5.1i |
On Thu 26 Jun 2003 (15:45 +0200), Mueller, Achim wrote:
> Hi folks,
>
> while doing longer rollouts gnubg segfaults when switching from one
> selected move to another.
>
> OS: Linux (gentoo, RedHat, SuSE)
> gnubg-devel (0,.14)
>
> I compiled gnubg with the option -g and started it out of the gdb doing
> another big rollout. (Un)fortunately it now works for 2 days without
> exiting.
>
> Any idea t get output or more information?
Don't bother running it under gdb. If it segfaults, you should get a
core file in the directory you were in. Then change to the source
directory for gnubg and run gdb <path of gnubg> <path of core file> -
for example:
/home/jes/gnubg% gdb /usr/local/bin/gnubg /home/jes/gnubg.core
If you can post the output from gdb's 'bt' command and a copy of the
game file being rolled out with an indication of the game and move
within the game where the crash occurred, then there is a start on
locating the problem.
If anyone can find a way to reproduce the problem, then finding and
fixing it is usually not too hard.
It's possible that it's a memory management problem, these can be very
nasty as freeing a block of memory and continuing to use it can
produce crashes at a point long after the incorrect free/use.
--
Jim Segrave address@hidden