Bug#863536: doomsday: Segfaults when attempting to start new game

2017-06-01 Thread Markus Koschany
Control: tags -1 pending Am 31.05.2017 um 20:12 schrieb Bernhard Übelacker: > Hello, > tried to reproduce the issue. > > I think the problem is that in Cl_IsClientMobj the method maybeAs() > is called on a NULL pointer on mo->thinker.d. > > With the attached patch the crash does not happen. > >

Bug#863536: doomsday: Segfaults when attempting to start new game

2017-05-31 Thread Bernhard Übelacker
Hello, tried to reproduce the issue. I think the problem is that in Cl_IsClientMobj the method maybeAs() is called on a NULL pointer on mo->thinker.d. With the attached patch the crash does not happen. And this time I took the opportunity to play in doom1-share.wad and doom2.wad (just short) and

Bug#863536: doomsday: Segfaults when attempting to start new game

2017-05-28 Thread Hans Joachim Desserud
Package: doomsday Version: 1.15.8-4 Severity: important Dear Maintainer, Thanks for resolving https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847651. I no longer get a segfault at startup, but I do see one when attempting to start a new game: ^ : Starting music 'intro' fluidsynth: warning