It just happened and oddly doesn't create a core file. It's basically a while loop to run mamer on crash (line 4 being the bin/mamer).
Here is what happened though (again during open of the tourney when people are still joining).
./runmamer.sh: line 4: 8758 Segmentation fault (core dumped) bin/mamer
Mamer crashed with exit code 139. Restarting ..
--------------------------------------------------------------------
Edit: Looking up more info seems that this is a Segfault 11 (in linux land) which is a memory access problem. Will try compiling it again using valgrind to get more info.
A mamer replacement - what would it have to do?
Moderator: Ras
-
jshriver
- Posts: 1375
- Joined: Wed Mar 08, 2006 9:41 pm
- Location: Morgantown, WV, USA
-
hgm
- Posts: 28461
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: A mamer replacement - what would it have to do?
It is indeed very weird that it says 'core dumped' while there is no code dump. Are you sure you looked for it in the right directory (perhaps it changed its current directory after startup)? Or could there be a problem with writing permission in those directory, because they are owned by another user as you were when starting up mamer?
-
ZirconiumX
- Posts: 1361
- Joined: Sun Jul 17, 2011 11:14 am
- Full name: Hannah Ravensloft
Re: A mamer replacement - what would it have to do?
tu ne cede malis, sed contra audentior ito