[deleted]
Moderator: GZDoom Developers
Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
Re: Segfault on Release build of 4.1.2
GZDoom should create a crash report. Most likely, you don’t have GDB installed if a report wasn’t saved.
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
Re: Segfault on Release build of 4.1.2
I just checked and gdb is installed on the machine that runs gzdoom. It's not installed in the docker image. I'll try doing that before building gzdoom.
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
Re: Segfault on Release build of 4.1.2
Okay, I just tried building both the debug and release versions with gdb installed in the docker container and it made no difference to the resulting binary.
I also just attempted running gzdoom with gdb attached. With the release version, gdb rightfully complained that no debugging symbols were found. When the segfault occurred, it didn't give any additional information as it wasn't able to identify where the segfault occurred. The symbol it gave was "??".
When I ran the debug version with gdb attached, it was able to find the debugging symbols, but no segfault occurred.
I also just attempted running gzdoom with gdb attached. With the release version, gdb rightfully complained that no debugging symbols were found. When the segfault occurred, it didn't give any additional information as it wasn't able to identify where the segfault occurred. The symbol it gave was "??".
When I ran the debug version with gdb attached, it was able to find the debugging symbols, but no segfault occurred.
Last edited by newestuser on Sun Jun 09, 2019 9:35 pm, edited 1 time in total.
Re: Segfault on Release build of 4.1.2
If GDB is installed on the system where GZDoom is running, have no idea why crash report isn't generated.
You can run GZDoom under GDB, and do bt command right after the crashes.
There will be no source line information in Release build, but symbols (i.e. function names) should be there.
Also, you can try to use RelWithDebInfo configuration instead of Release.
You can run GZDoom under GDB, and do bt command right after the crashes.
There will be no source line information in Release build, but symbols (i.e. function names) should be there.
Also, you can try to use RelWithDebInfo configuration instead of Release.
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
Re: Segfault on Release build of 4.1.2
Well, it's better that nothing. The problem is I have no idea how this can happen.
I expected that it's a bug of GCC optimization for Release build. RelWithDebInfo is more stable usually.
If you want to help with this issue, you can try to build with address sanitizer enabled.
Just add -DWITH_ASAN=YES command line switch to cmake invocation.
Build and run as usual, it should output lots of information after an error.
I expected that it's a bug of GCC optimization for Release build. RelWithDebInfo is more stable usually.
If you want to help with this issue, you can try to build with address sanitizer enabled.
Just add -DWITH_ASAN=YES command line switch to cmake invocation.
Build and run as usual, it should output lots of information after an error.
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
Re: Segfault on Release build of 4.1.2
I suspected that there will a memory corruption reported by ASAN, but the problem seems to be different here.
Could you please post your configuration .ini file?
Could you please post your configuration .ini file?
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
-
newestuser
- Posts: 9
- Joined: Sat Jun 08, 2019 5:41 pm
- Graphics Processor: Intel (Modern GZDoom)
Re: [GZDoom 4.1.2] [GZDoom 4.1.3] Segfault on Release build
I have a similar issue here. Release and RelWithDebInfo builds both error out on exit with similar error codes.
*** Error in `/home/pfred1/Build/gzdoom/GZDoom2/gzdoom/build/gzdoom': free(): invalid pointer: 0x000055cc3e923cd0***
*** Error in `/home/pfred1/Build/gzdoom/GZDoom2/gzdoom/build/gzdoom': free(): invalid pointer: 0x00005588ba907cb0 ***
Debug and MinSizeRel builds do not issue an error on exit. So it looks like something to do with optimization? I'll have to try to build with a different compiler.
Right now I am using gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
*** Error in `/home/pfred1/Build/gzdoom/GZDoom2/gzdoom/build/gzdoom': free(): invalid pointer: 0x000055cc3e923cd0***
*** Error in `/home/pfred1/Build/gzdoom/GZDoom2/gzdoom/build/gzdoom': free(): invalid pointer: 0x00005588ba907cb0 ***
Debug and MinSizeRel builds do not issue an error on exit. So it looks like something to do with optimization? I'll have to try to build with a different compiler.
Right now I am using gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
Re: [GZDoom 4.1.2] [GZDoom 4.1.3] Segfault on Release build
Post a callstack please.