Menu
▾
▴
Re: [GalaxyNG-Developers] Fwd: GalaxyNG CVS to Git conversion
|
From: John W. <jwo...@ac...> - 2019-12-02 17:00:01
|
How goes GalaxyNG?
On 9/18/2018 3:14 PM, Steve Webb wrote:
> Hey! The stable branch is the way to go! I got it all up and running
> again! Woohoo! :)
>
> - Steve
>
> On Mon, Sep 17, 2018 at 4:16 PM Chris Shaffer <chr...@gm...
> <mailto:chr...@gm...>> wrote:
>
> I’m not sure if trilarion, who sent the original email, is on this
> list.
> On Mon, Sep 17, 2018 at 2:38 PM Aaron Scott-Boddendijk
> <ta...@gm... <mailto:ta...@gm...>> wrote:
>
> There is a 'stable' branch too that supposedly is what one of
> the servers was actually running.
>
> I wouldn't at all be surprised if fixes are needed though.
> I'll see whether I can get any further - though if anyone
> spots anything please do raise a PR while we decide where the
> code should live permanently.
>
> On Tue, Sep 18, 2018 at 9:05 AM Steve Webb <bi...@gm...
> <mailto:bi...@gm...>> wrote:
>
> Well, bad news unfortunately.
>
> I got galaxyng compiled on Ubuntu 16.04 (64-bit) and ran
> the "-template" command, and got and edited a template.
> Everything went well until I ran the "-create" command and
> got a core dump. :(
>
> I wondered if it was a 64/32 bit problem, so I found out
> how to compile and link it using all 32-bit stuff and
> turned off all of the libgd stuff but it still core-dumped
> at the same point, so it may be a new compiler
> optimization thing maybe?
>
> (gdb) set args -create pre01.glx
> (gdb) run
> Starting program: /home/steve/Games/galaxyng -create pre01.glx
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0806ceb2 in addListF ()
> (gdb) bt
> #0 0x0806ceb2 in addListF ()
> #1 0x0804b8ca in readGameSpec (specfile=0x8085030) at
> create.c:151
> #2 0x0806a737 in CMD_create (argc=3, argv=0xffffd6a4) at
> cmd_create.c:30
> #3 0x080494b4 in main (argc=3, argv=0xffffd6a4) at
> galaxyng.c:139
>
> (gdb) break create.c:150
> Breakpoint 1 at 0x804b8a1: file create.c, line 150.
>
> (gdb) run
> The program being debugged has been started already.
> Start it from the beginning? (y or n) y
> Starting program: /home/steve/Games/galaxyng -create pre01.glx
>
> Breakpoint 1, readGameSpec (specfile=0x8085030) at
> create.c:150
> 150 aNewPlayer->pswd = strdup( raceName );
> (gdb) list
> 145 ( aGameSpec->numberOfPlayers )++;
> 146 sprintf( raceName, "race_%d",
> 147 aGameSpec->numberOfPlayers );
> 148 setName( aNewPlayer, raceName );
> 149 sprintf( raceName, "P%d", rand( ) );
> 150 aNewPlayer->pswd = strdup( raceName );
> 151 addList( &( aGameSpec->players ),
> aNewPlayer );
> 152 aNewPlayer->coreSizes =
> 153 malloc( 10 * sizeof( double ) );
> 154 memset( aNewPlayer->coreSizes, 0,
> (gdb) print raceName
> $1 = "P867346957\000\377\204\214\a\b\001\000\000"
> (gdb) print aNewPlayer
> $2 = (newplayer *) 0x8086270
> (gdb) print *aNewPlayer
> $3 = {next = 0x0, cookie = 0, name = 0xf1ea5747 <error:
> Cannot access memory at address 0xf1ea5747>, addr =
> 0x80862b8 "race_1", pswd = 0x0, numberOfHomePlanets = 0,
> coreSizes = 0x0, coreXOffset = 0x0, coreYOffset = 0x0,
> team = 0, done = 0}
> (gdb) n
> 151 addList( &( aGameSpec->players ),
> aNewPlayer );
> (gdb) print aNewPlayer
> $4 = (newplayer *) 0x8086270
> (gdb) print *aNewPlayer
> $5 = {next = 0x0, cookie = 0, name = 0xf1ea5747 <error:
> Cannot access memory at address 0xf1ea5747>, addr =
> 0x80862b8 "race_1", pswd = 0x80862c8 "P867346957",
> numberOfHomePlanets = 0, coreSizes = 0x0, coreXOffset =
> 0x0, coreYOffset = 0x0, team = 0, done = 0}
>
> I'm wondering if it's the "cannot access memory at ..."
> errors.
>
> to recreate:
>
> git clone gi...@gi...:Talden/galaxyng.git
> <mailto:gi...@gi...:Talden/galaxyng.git>
> cd galaxyng
> # you may have libgd issues, so uncomment the ADDTL_*
> lines from Source/Makefile and
> # remove influence.c from GNG_SRCS to completely remove
> the influence map and libgd stuff
> make
> make install
> cd ~/Games
> ./galaxyng -template blah 4
> ./galaxyng -create blah.glx
>
> - Steve Webb
>
> On Sun, Sep 16, 2018 at 5:34 AM Aaron Scott-Boddendijk
> <ta...@gm... <mailto:ta...@gm...>> wrote:
>
> I've made a quick conversion and then split into what
> are hopefully logical pieces (as some might prove to
> be abandonware in the long-run).
>
> Todo
> 1. Sign up and transfer the repos to a GalaxyNG
> account that a maintainer can hold
> 2. Add Readme's to each repo with at least License and
> Source information - ideally adding a blurb about the
> content purpose and maintenance intentions (I expect
> some are abandonware)
> 3. Find out which commit people are actually running
> and tag it as a known stable release.
> 4. Add a getting started with building (maybe with
> some notes on building and running in a docker
> container - likely easier for Windows participants to
> deal with dependencies)
>
|
