Nick Allen nick.allen...@gmail.com writes:
Sorry, most of the technical stuff referred to is above my head, but I
may be able to help with an explanation of why the technical people
put a loop in.
At one point, when the age limit for a tile was reached, and the
programme was started, it
Nick Allen nick.allen...@gmail.com writes:
Sorry, most of the technical stuff referred to is above my head, but I
may be able to help with an explanation of why the technical people
put a loop in.
At one point, when the age limit for a tile was reached, and the
programme was started, it
] Segmentation fault with git HEAD
Date: Sun, 22 Jun 2014 13:35:49 +0200
From: em...@gmx.net
To: viking-devel@lists.sourceforge.net
Subject: [Viking-devel] Segmentation fault with git HEAD
Not sure if the intention is that the Viking git master branch is
always clean but I did try it anyhow.
I
] Segmentation fault with git HEAD
Date: Sun, 22 Jun 2014 13:35:49 +0200
From: em...@gmx.net
To: viking-devel@lists.sourceforge.net
Subject: [Viking-devel] Segmentation fault with git HEAD
Not sure if the intention is that the Viking git master branch is
always clean but I did try it anyhow.
I compiled
Date: Sun, 22 Jun 2014 13:35:49 +0200
From: em...@gmx.net
To: viking-devel@lists.sourceforge.net
Subject: [Viking-devel] Segmentation fault with git HEAD
Not sure if the intention is that the Viking git master branch is
always clean but I did try it anyhow.
I compiled the code
Not sure if the intention is that the Viking git master branch is always
clean but I did try it anyhow.
I compiled the code based on git index 4200b261[*] and see that I can
easily trigger a Segmentation fault:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread
