Re: [tsc-devel] Re: Bad build?

Marvin Gülker | Fri, 05 Aug 2016 17:57:24 UTC

Hi,

please reply to the actual message and not send a new email. Without the
"References:" headers being set correctly (by means of replying), the
thread view gets screwed up (your email does not appear part of the
thread). You already did that better before :-)

Also, take a look at how I quote when I reply on the ML. What you do is
called top-posting and it disturbs the logical flow of things.

On Fri, Aug 05, 2016 at 09:18:46PM +1000, SK K wrote:
> To check again I did a fresh clone just  a few moments before
> and again got the same error. This happens as soon as i hit enter on the
> worldmap.

This does not seem right. When updating, did you update the Git
submodules? If not, do it like this and then recompile:

   $ git submodule update

I pushed an mruby submodule update in one of the more recent
commits. Maybe you have missed that one.

If you did update your submodules, we'll need to do some
debugging. First, please try loading lvl_1 directly from the level menu
(not from the world map). If it still crashes, you'll need to run the
game in GDB and produce a backtrace we as the developers can work
with. After installing GDB with your distribution's package manager, you
can do so like this:

  $ gdb ./path/to/tsc
  (gdb) r
  ...now play until it crashes...
  program received SIGABRT.
  (gdb) bt
  ...now comes the backtrace...
  (gdb) q

GDB will only produce a useful backtrace if you compiled TSC with
debugging symbols (-DCMAKE_RELEASE_TYPE=Debug). You'll need to recompile
TSC if you didn't. Once you have obtained the backtrace, please post it
so we can take a look at it.

Vale,
Quintus

-- 
Blog: http://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F