Dear Maintainer,
I tried to have a look, but got no clue why a Unwind should take place
until I saw the old build log [1].
There I found this warning:
Levels.cpp: In member function ‘bool Levels::addLevel(const string&, int,
int)’:
Levels.cpp:118:1: warning: no return statement in function r
Just for reference, why g++ does not error here,
this gcc bug might be interesting:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43943
Kind regards,
Bernhard
I can confirm this, and the backtrace looks similar:
#0 0x00080005 in ?? ()
#1 0x77a1d879 in _Unwind_ForcedUnwind_Phase2 (exc=0x55614e90,
context=0x7fffdd70, frames_p=0x7fffdc78) at
../../../src/libgcc/unwind.inc:170
#2 0x77a1e14d in _Unwind_Resume (exc=exc
here the backtrace
Type "apropos word" to search for commands related to "word"...
Reading symbols from numptyphysics...
Reading symbols from
/usr/lib/debug/.build-id/1c/669beb5cdc6578b37b1e53e575baefe21524ff.debug...
(gdb) r
Starting program: /usr/games/numptyphysics
[Thread debugging using li
Package: numptyphysics
Version: 0.2+svn157-0.4
Severity: grave
X-Debbugs-Cc: pi...@debian.org
the prgram do not start and crash at startup
-- System Information:
Debian Release: bullseye/sid
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500,
5 matches
Mail list logo
