[Scummvm-tracker] [ScummVM] #9705: FULLPIPE: Crash on start

Colin Snover trac at scummvm.org
Sun Nov 19 20:22:21 CET 2017


#9705: FULLPIPE: Crash on start
----------------------+------------------------------
  Reporter:  raziel-  |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  blocker  |  Component:  Engine: Fullpipe
Resolution:           |   Keywords:  has-backtrace
      Game:           |
----------------------+------------------------------

Comment (by csnover):

 According to that backtrace, the crash is happening inside of newlib,
 again failing to allocate memory just like before, but at a different
 place. I had hoped the reduced number of heap allocations and
 significantly reduced memory leakage in the latest code would have
 improved the situation, but it still seems like the system is having
 memory trouble. If this is the case, it is ''probably'' not a ScummVM bug
 at this point since the game startup doesn’t leak at this point according
 to instrumentation.

 There is some cruft in `configure` that changes the way that AmigaOS
 builds work which might be causing trouble, like forcing static linkage
 and making other changes to compiler flags which may not be needed with
 the more modern GCC 5 compiler you’re using, so maybe a place to start
 would be get rid of these lines for the AmigaOS backend in `configure` and
 try recompiling:

 {{{
 append_var CXXFLAGS "-mlongcall"
 LDFLAGS=`echo $LDFLAGS | sed 's/-use-dynld//'`
 append_var LDFLAGS "-static"
 }}}

 and maybe this one too:

 {{{
 append_var LDFLAGS "-Wl,--export-dynamic"
 }}}

 You might also try using `configure --enable-plugins --default-dynamic` to
 reduce the size of the ScummVM image in memory, to allow the game to have
 more memory, and/or `-Os` for the optimisation flag to have the compiler
 optimise the image size a bit more.

 Let me know if any of that makes a difference, otherwise you will probably
 need to complain upstream (there’s not much we can ''reasonably'' do to
 work around bugs in the system’s memory allocator, if that’s what’s
 happening, which it appears so). Thanks!

--
Ticket URL: <https://bugs.scummvm.org/ticket/9705#comment:9>
ScummVM <https://bugs.scummvm.org>
ScummVM


More information about the Scummvm-tracker mailing list