From: ben-cooper <ben-cooper@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] gnuchess segfaults on first move
Date: Wed, 20 Jan 2021 02:57:15 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28044@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
New issue by ben-cooper on void-packages repository
https://github.com/void-linux/void-packages/issues/28044
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.10.8_1 x86_64-musl AuthenticAMD uptodate rrnFFFF
* package:
gnuchess-6.2.7_1
### Expected behavior
The program should be able to play a game of chess with me.
### Actual behavior
The program is able to detect illegal moves, but after I play the first move, it segfaults after thinking about what to play. It renders my move correctly on the text board, however. This behaviour is also present when using the program `gnome-chess`.
```
GNU Chess 6.2.7
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
White (1) : e4
1. e4
black KQkq e3
r n b q k b n r
p p p p p p p p
. . . . . . . .
. . . . . . . .
. . . . P . . .
. . . . . . . .
P P P P . P P P
R N B Q K B N R
Thinking...
Segmentation fault
```
### Steps to reproduce the behavior
1. Run `gnuchess`
2. Play any legal move (such as e4)
next reply other threads:[~2021-01-20 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 1:57 ben-cooper [this message]
2021-01-20 2:14 ` [ISSUE] [CLOSED] " ericonr
2021-01-20 2:15 ` ericonr
2021-01-20 2:25 ` ben-cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28044@inbox.vuxu.org \
--to=ben-cooper@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).