bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] Building on Ubuntu 14.04 : Temporary Workaround


From: Philippe Michel
Subject: Re: [Bug-gnubg] Building on Ubuntu 14.04 : Temporary Workaround
Date: Thu, 23 Jul 2015 21:22:30 +0200 (CEST)
User-agent: Alpine 2.20 (BSF 67 2015-01-07)

On Thu, 23 Jul 2015, Michael Petch wrote:

It appears the problem is related to a change since 1.05.000 was
released. It appears the code at the head of CVS is causing some issue.

Did you just rebuild 1.05 on an up to date Ubuntu 14.04 or do you mean you had checked that it worked back then ?


I seem to have a similar problem on Ubuntu 15.04 :

(gdb) run -t
Starting program: /home/pm/gnubg-1.05.000/gnubg -t
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
GNU Backgammon 1.05.000  Jul 20 2015
Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 by Gary Wong.
Copyright (C) 2015 by Gary Wong and the AUTHORS; for details type `show 
version'.
This program comes with ABSOLUTELY NO WARRANTY; for details type `show 
warranty'.
This is free software, and you are welcome to redistribute it under certain 
conditions; type `show copying' for details.
^C
Program received signal SIGINT, Interrupt.
memset (__dest=0x8227ac0, __ch=0, __len=512)
    at /usr/include/i386-linux-gnu/bits/string3.h:90
90        return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest));
(gdb) where
#0  memset (__dest=0x8227ac0, __ch=0, __len=512)
    at /usr/include/i386-linux-gnu/bits/string3.h:90
#1  0x0808e5f4 in memset (__len=512, __ch=0, __dest=<optimized out>)
    at /usr/include/i386-linux-gnu/bits/string3.h:90
#2  MT_CreateThreadLocalData (id=0) at mtsupport.c:51
#3  0x0808e8cb in MT_InitThreads () at mtsupport.c:362
#4  0x0804d0dc in main (argc=1, argv=0xbffff074) at gnubg.c:4615
(gdb) quit


I'm quite sure it used to work after the 1.05 release (my ubuntu 15 VM is probably more recent than this) and there were very few changes since then anyway.

My guess is that something in a recent update to Ubuntu exposes a bug that was already there.



reply via email to

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