ZDoom

The FreeBSD version works just fine, no errors.

I tried to bring it to OpenBSD though, and got an exec error. [url=https://www.sendspace.com/file/0wxk8l]This is an executable, if anyone else is interested.[/url] (You might need an ad blocker, sendspace has some nasty ads) It was compiled in FreeBSD - I would've thought it SHOULD work just fine in OpenBSD. Guess I was wrong.

I'll take a look.

[quote="Rachael"]Unfortunately it was still outputting the same style of debugging information as before, and GDB still said it was "corrupted" (was it really?)

I'm taking a break from this, for now, getting a bit frustrated with it and I need to rest.

If anyone else wants to try it, here's a few notes about OpenBSD's X environment:

If you don't mind a garishly-looking desktop, deploying OpenBSD with a simple X server with Xterm for the purposes of debugging is pretty easy to do. If you need something a little bit more modern-looking though, there are metapackages available for Xfce, MATE, Cinnamon, KDE, and a few other familiar desktop environments.

As a note, though, OpenBSD's default X server starts in "retro" mode, so if you don't have something to change the wallpaper it's going to irritate your eyes very quickly. (Personally, I just use putty with VcXSrv and SSH in and get a desktop environment that way, it's a lot easier for me)[/quote]

Would it be easy for you to confirm if FreeBSD + Hexen behaves similarly? More than happy to debug it from there, but locating my Hexen media is going to be a little bit of a bear that I'd rather not poke unless I need to. =) Also understandable if you'd rather not try this combination, of course.

Unfortunately it was still outputting the same style of debugging information as before, and GDB still said it was "corrupted" (was it really?)

I'm taking a break from this, for now, getting a bit frustrated with it and I need to rest.

If anyone else wants to try it, here's a few notes about OpenBSD's X environment:

If you don't mind a garishly-looking desktop, deploying OpenBSD with a simple X server with Xterm for the purposes of debugging is pretty easy to do. If you need something a little bit more modern-looking though, there are metapackages available for Xfce, MATE, Cinnamon, KDE, and a few other familiar desktop environments.

As a note, though, OpenBSD's default X server starts in "retro" mode, so if you don't have something to change the wallpaper it's going to irritate your eyes very quickly. (Personally, I just use putty with VcXSrv and SSH in and get a desktop environment that way, it's a lot easier for me)

You can specify additional compiler options via [b]-DCMAKE_C_FLAGS=...[/b] and [b]-DCMAKE_CXX_FLAGS=...[/b] in command line.

Recompiling now... really wish I didn't have to edit CMakeLists.txt to do that.

You can try to add [url=https://clang.llvm.org/docs/UsersManual.html#controlling-debugger-tuning]-ggdb[/url] compiler switch instead.

EDIT: And [url=https://clang.llvm.org/docs/ClangCommandLineReference.html#kind-and-level-of-debug-information]-gdwarf-2[/url] may help too.

I'm investigating installing LLDB on it now, but it's possible I may have to do that manually. Hopefully it's not going to make me clone the entire LLVM repository to get it - because that behemoth is a bloody nightmare to manage, especially on a virtual machine, even as lightweight as OpenBSD is.

Compiler is good but the version of GDB is quite old. Does it have a newer version or LLDB maybe?

OpenBSD clang version 5.0.1 (tags/RELEASE_501/final) (based on LLVM 5.0.1)
Target: amd64-unknown-openbsd6.3
Thread model: posix
InstalledDir: /usr/bin

This is what mine says:
[code]OpenBSD clang version 5.0.1 (tags/RELEASE_501/final) (based on LLVM 5.0.1)
Target: amd64-unknown-openbsd6.3
Thread model: posix
InstalledDir: /usr/bin
[/code]

Seems like GDB was unable to parse debug information.

I saw similar issues with custom built GCC on PowerPC Mac.
The only solution I found is to lower version of DWARF via command line for compiler.

This could be a totally different problem though. Probably it's a side effect of memory corruption.

BTW what's the version of GCC or Clang is used?

Master is the active development branch, so it will always be newer than a tag.

Anyway - I went ahead to give it a go - unfortunately, my experience in debugging with POSIX tools is absolutely nil. :( But I got the error.

[imgur]https://imgur.com/28DQupo[/imgur]

Hoping someone who is proficient with gdb can possibly help me trace the error.

haha i understand, i dont play with it myself even, i used to play with prboom and chocolate hexen for many many time, but now i like a little newer experience and i am using ketchup mod only for replaying some maps, i only tested it because that i know that a lot of people love it, thats why i was testing a little of everything myself.

At home i will test the master branch instead of the g3.3.2 to check if i can see if the errors are still there, but i suppose that master is older than tag g3.3.2 right or is the other way around right now?

Thanks for everything!

I tested the master branch for GZDoom, directly. I didn't use mods though, my OpenBSD setup is rather bare and currently only contains shareware Doom in order to test the rendering output.

I'll test Hexen though. I am sorry but I really want to distance myself from Brutal Doom and would avoid it at all costs if I can, I'll only load it if I absolutely have to and there's no other way.

[quote="Rachael"]Alright. I'm going to do a test compile of master, myself, really quick, and if there are any changes needed I'll push them.

EDIT: My compile was successful and so far I haven't had any problems in my tests.[/quote]

Thank you! but thats unexpected for me, dont you face the same problems i am facing? with the mods and hexen wad?

EDIT: I forget to say it, but i had compiled earlier the g3.3.2 git tag for GZDoom, and master for QZDoom, which one did you test?