Welcome to the ZDoom Forums!

Are those of you with this issue using Xorg 1.5? (For Ubuntu that's version 8.10 or newer)

If you are you might want to try adding the following to your xorg.conf:
Section "Module"
...
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
...
EndSection
Courtesy of Gentoo's Xorg 1.5 ...

I uncommented that code and found that the problem line is actually this one:
print (s:"\cCThis Door can't be opened!");

I'd guess the new include code (responsible for that warning I fixed) has screwed things up. I made sure that my fix did not create this problem, so this issue has also existed ...

I noticed this warning when compiling acc:
gcc -Os -Wall -W -fomit-frame-pointer -c -o token.o token.c
token.c: In function 'TK_AddIncludePath':
token.c:323: warning: comparison between pointer and integer

The problem is that the comparison, as written, is trying to compare a string to a ...

I've attached a patch with a fix for the error and the warning below.
Compiling texturemanager.cpp: [ERROR]
g++ -pipe -Wall -Wno-unused -fno-strict-aliasing -MMD -DHAVE_FILELENGTH -D__forceinline=inline -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0 ...

I'm sure nobody's interested in what I'm doing. Hahaha, the Dragon Book ! I'm surprised I even recognized it. Some professor a few years back gave a ten minute spiel on it during one presentation.
That's the 1986 version. The latest edition is from 2006 and now covers a few additional topics that ...

Yes, I thought about it after I posted and came to a similar conclusion. However, I wanted to hear your take on it.

Then again, Valgrind deals better with this than the Mudflap pointer debugging option built into GCC. Actually, I've been unable to produce a binary with Mudflap that will even start ...

With startup/shutdown out of the way, I started a new game in Strife under valgrind and it shows a series of invalid writes at r_segs.cpp:1075.
+MAP02 - AREA 2: town

Terminated sig=0x0f
Playing /tmp/zmidojOgVG
MIDI file: /tmp/zmidojOgVG
Format: 0 Tracks: 1 Divisions: 70
==11740==
==11740 ...

Randy, valgrind indicates a number of memory leaks within ZDoom. Attached is my log from starting ZDoom up and then quitting. Of course, you could try this yourself too, since you've several Linux setups now.

It also crashed on exit:
==13658== Invalid read of size 2
==13658== at 0x8194216: S ...

$ gdb zdoomd
GNU gdb 6.7.1
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and ...

Compiling gameconfigfile.cpp: [ERROR]
g++ -fno-rtti -pipe -Wall -Wno-unused -fno-strict-aliasing -O2 -fomit-frame-pointer -MMD -DHAVE_FILELENGTH -D__forceinline=inline -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr ...

snes_spc/Makefile should be be reverted to r995, since it seems Randy has accidentally replaced it with the new dumb Makefile (dumb/Makefile).

The crash is finally gone in the latest version, with the changes made on May 13.

I was going to say that I'm not really sure that this crash has much to do with the fact that you've compiled a 64-bit version, as I haven't even been able to start ZDoom for awhile now. (It crashes after choosing the iwad, but before bringing up video.)

So anyway, I decided to compile a version ...

Compile a debug version of ZDoom like so: Then, crash ZDoom again and attach the resulting zdoom-crash.log to a message.

Compiling fmodsound.cpp: [OK]
src/sound/fmodsound.cpp: In constructor 'FMODStreamCapsule::FMODStreamCapsule(FMOD::Sound*, FMODSoundRenderer*, const char*)':
src/sound/fmodsound.cpp:521: warning: 'FMODStreamCapsule::Ended' will be initialized after
src/sound/fmodsound.cpp:520: warning: 'FString ...