[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XBoard-devel] Connecting to ICS through gateway broken?

From: Michel Van den Bergh
Subject: Re: [XBoard-devel] Connecting to ICS through gateway broken?
Date: Mon, 13 Jun 2011 07:29:27 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101028 Thunderbird/3.1.6


Yes that should explain it. Should be simple to patch.


On 06/12/2011 11:07 PM, Tim Mann wrote:
I tried it under gdb and the segfault is here:

Program received signal SIGSEGV, Segmentation fault.
0x000000000040972b in establish () at ../backend.c:1680
1680            if (*appData.remoteUser == NULLCHAR) {
(gdb) where
#0  0x000000000040972b in establish () at ../backend.c:1680
#1  0x0000000000408e87 in InitBackEnd3 () at ../backend.c:1477
#2  0x000000000040855c in InitBackEnd2 () at ../backend.c:1320
#3  0x0000000000451d66 in main (argc=6, argv=0x7fffffffe2a8)
    at ../xboard.c:2670
(gdb) print appData.remoteUser
$1 = 0x0

So it's probably an issue with the (relatively) new command line parsing. Most likely the remoteUser used to default to "" and now it defaults to NULL.

Interestingly, the current command line parsing rejects "" for some reason:

$ xboard -gateway localhost -ics -icshost freechess.org -remoteUser ""
xboard: No value provided for argument -remoteUser

That's a bug too -- "" is an empty string; it's not "no value".

Providing your actual username does work around the issue, though:

$ xboard -gateway localhost -ics -icshost freechess.org -remoteUser "mann"
Connected to freechess.org.

On Sun, Jun 12, 2011 at 11:02 AM, Michel Van den Bergh <address@hidden> wrote:
On 06/12/2011 07:55 PM, Michel Van den Bergh wrote:
The following command segfaults with xboard 4.5.0

xboard -ics -gateway -icshost freechess.org

However it works fine on 4.2.7.

This is a modern Linux system so rsh is really ssh.

BTW this gateway feature is mighty cool!


xboard just seems to execute the command

rsh telnet freechess.org 5000

So it might be an issue with string handling in 4.5.0.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]