Glad to hear that!
Antonio
On Sun, Jun 13, 2021 at 6:57 PM victorhck wrote:
> El 23/10/20 a las 20:16, Antonio Ceballos escribió:
> > I could not reproduce the bug on Ubuntu 16.04, but I could on Debian
> 10.6.
> >
> > I have verified Simon's patch and I think it is fine and fixes the bug.
> >
El 23/10/20 a las 20:16, Antonio Ceballos escribió:
> I could not reproduce the bug on Ubuntu 16.04, but I could on Debian 10.6.
>
> I have verified Simon's patch and I think it is fine and fixes the bug.
>
> Therefore, I have uploaded the change to the subversion repository in
> Savannah. It wil
El 23/10/20 a las 20:16, Antonio Ceballos escribió:
> I could not reproduce the bug on Ubuntu 16.04, but I could on Debian 10.6.
>
> I have verified Simon's patch and I think it is fine and fixes the bug.
>
> Therefore, I have uploaded the change to the subversion repository in
> Savannah. It wil
I could not reproduce the bug on Ubuntu 16.04, but I could on Debian 10.6.
I have verified Simon's patch and I think it is fine and fixes the bug.
Therefore, I have uploaded the change to the subversion repository in
Savannah. It will be included in the next release, 6.2.8, which may still
take a
This seems to be FORTIFY_SOURCE compiler flag. Debian sets level 2, but just level 1 triggers it.The code uses sprintf to concatenate strings which is "undefined" behaviour, the offending code is flagged by enabling all compiler warnings when building pgn.ccThis explains why it wasn't caught in dev
Thanks for your answer. We will try to track it down.
Antonio
On Wed, Oct 7, 2020 at 5:52 PM victorhck wrote:
> El 7/10/20 a las 0:27, Antonio Ceballos escribió:
> > Hello,
> >
> > I have been unable to reproduce the problem on version 6.2.7.
> >
> > I don't understand where the two-line date
El 7/10/20 a las 0:27, Antonio Ceballos escribió:
> Hello,
>
> I have been unable to reproduce the problem on version 6.2.7.
>
> I don't understand where the two-line date heading of your ARCHIVO
> comes from, as pgnsave does not write anything before [Event ""]. Do
> you have any clue? By the wa
I can always reproduce in Debian packaged 6.2.5, but not in 6.2.7 from source.
I'll check the build options if I get more time. or probably just build 6.2.7
using the Debian source package, so it is built with the same options, unless
Antonio thinks there is relevant changes.
Hello,
I have been unable to reproduce the problem on version 6.2.7.
I don't understand where the two-line date heading of your ARCHIVO
comes from, as pgnsave does not write anything before [Event ""]. Do
you have any clue? By the way, had you invoked pgnload beforehands?
As Simon said, PGNSaveT
Hello.
Don't know if it's a bug or maybe I'm doing something wrong when I save
a game.
I run gnuchess and doing some moves. If I run show game, I can see the
moves. But if I run pgnsave that only saves the last move, so after I
can't load.
running show game after some moves:
@Blancas (4) : show
On Wednesday, 30 September 2020 17:14:27 BST victorhck wrote:
> Hello.
>
> Don't know if it's a bug or maybe I'm doing something wrong when I save
> a game.
Thanks for the report, looks like a straight bug to me. Quick look I think the
PGNSaveToFile does some weird things if comments exist that
Hello.
Don't know if it's a bug or maybe I'm doing something wrong when I save
a game.
I run gnuchess and doing some moves. If I run show game, I can see the
moves. But if I run pgnsave that only saves the last move, so after I
can't load.
running show game after some moves:
@Blancas (4) : show
12 matches
Mail list logo