this version of HD
Code: Select all
gzdoom -file [path to HD] -nomusic -noautoload +map range
3.1.0 does not do this at all.
Compiled GZDoom as "Debug".
Moderator: GZDoom Developers
Code: Select all
gzdoom -file [path to HD] -nomusic -noautoload +map range
Code: Select all
gzdoom -file [path to HD] -nomusic -noautoload +map range +set playerclass "enforcer"
gzdoom -file [path to HD] -nomusic -noautoload +map range +set playerclass "marksman"
This crash no longer happens if I compile as Release rather than Debug, but another crash happens that is even more totally random.Vaecrius wrote:Compiled GZDoom as "Debug".
Code: Select all
*** Error in `/home/mchan223/doom/./gzdoom': free(): invalid next size (normal): 0x0000000003e8e090 ***
/home/mchan223/bin/gzdoom: line 2: 20818 Aborted ~/doom/./gzdoom $*
Code: Select all
p f->Func->PrintableName
p call->PrintableName
Code: Select all
gdb --args ./gzdoom -iwad doom2 -file hd <add any other command line options>
Code: Select all
...
[New Thread 0x7fffd3fff700 (LWP 31600)]
[Thread 0x7fffd3fff700 (LWP 31600) exited]
[New Thread 0x7fffd3fff700 (LWP 31603)]
[Thread 0x7fffd3fff700 (LWP 31603) exited]
Resolution: 1280 x 720
10 bots read from bots.cfg
map01 - entryway
[New Thread 0x7fffd3fff700 (LWP 31604)]
[Thread 0x7fffd3fff700 (LWP 31604) exited]
[New Thread 0x7fffd3fff700 (LWP 31605)]
[Thread 0x7fffd3fff700 (LWP 31605) exited]
[New Thread 0x7fffd3fff700 (LWP 31606)]
[Thread 0x7fffd3fff700 (LWP 31606) exited]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000f9205e in VMExec_Checked::Exec (stack=0x7ffff7fbe728,
pc=0x589c888, ret=0x7fffffffc760, numret=0)
at /home/mchan223/doom/gzdoom-7a1274ab768e2883da4ff988fc1f75604a6756c6/src/scripting/vm/vmexec.h:697
697 if (call->VarFlags & VARF_Native)
Code: Select all
(gdb) p f->Func->PrintableName
Cannot access memory at address 0x2b415f8
(gdb) p call->PrintableName
Cannot access memory at address 0x7fffffffbd88
Code: Select all
[New Thread 0x7fffd3fff700 (LWP 5258)]
[Thread 0x7fffd3fff700 (LWP 5258) exited]
Resolution: 1280 x 720
10 bots read from bots.cfg
map01 - entryway
[New Thread 0x7fffd3fff700 (LWP 5261)]
[Thread 0x7fffd3fff700 (LWP 5261) exited]
[New Thread 0x7fffd3fff700 (LWP 5262)]
[Thread 0x7fffd3fff700 (LWP 5262) exited]
[New Thread 0x7fffd3fff700 (LWP 5263)]
[Thread 0x7fffd3fff700 (LWP 5263) exited]
Program received signal SIGSEGV, Segmentation fault.
FName::operator== (this=0x103279988, other=...)
at /home/mchan223/doom/gzdoom-7a1274ab768e2883da4ff988fc1f75604a6756c6/src/./name.h:75
75 bool operator == (const FName &other) const { return Index == other.Index; }
(gdb) p f->Func->PrintableName
No symbol "f" in current context.
(gdb) p call->PrintableName
No symbol "call" in current context.
Code: Select all
[Thread 0x7fffd3fff700 (LWP 6298) exited]
[New Thread 0x7fffd3fff700 (LWP 6301)]
[Thread 0x7fffd3fff700 (LWP 6301) exited]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000835ae8 in GC::Mark(DObject**) ()
Try to disable completely the mouse in the menu. You should be able to see the cursor when you get a crash.Vaecrius wrote:I couldn't see my cursor at this time and decided not to risk being forced to reboot, so no attempt to call those p commands yet.
CLANG 3.5.0-10_mental_ wrote:EDIT: What is the compiler you are using? And its version please.
Code: Select all
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ ..;make -j 4
_mental_ wrote:Try to reproduce it again and when it hangs on black screen switch to GDB and press Ctrl+C there. Execute thread 1 and bt commands and post the output
Spoiler:
Spoiler:EDIT: For this one (which I'll call the "chainsaw crash" to distinguish it from the one in the OP) I can replace the imp in that summon with a vanilla Doom imp or demon and the crash still happens. It seems to happen much more frequently if I run GZDoom after making a change, then it crashes many times in a row before after a while I get a very long streak in which the crash doesn't happen at all.
Not necessarily, despite my inability to reproduce the crashes with the same compiler most likely it's a software bug.Vaecrius wrote:...is this a sign that my RAM is dying?