by PhysixCat » Fri Jul 05, 2019 10:18 am
Hello, I compiled the 4.1.3 release with the Debug flag enabled on Debian Sid according to the guide here
https://zdoom.org/wiki/Compile_GZDoom_o ... #Debugging. However, it seems that I'm getting stuck after trying to actually run GZDoom in the debugger tool
Code: Select all
ignacio@heim:~/data/gzdoom_build/gzdoom/build$ gdb ./gzdoom
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 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 "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./gzdoom...done.
(gdb) set logging on gzdoomdebug.log
Copying output to gzdoomdebug.log.
(gdb) run
Starting program: /home/ignacio/data/gzdoom_build/gzdoom/build/gzdoom
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff513d700 (LWP 9195)]
GZDoom g4.1.3 - 2019-06-08 07:56:19 -0400 - SDL version
Compiled on Jul 5 2019
Thread 2 "gzdoom" received signal SIG33, Real-time event 33.
[Switching to Thread 0x7ffff513d700 (LWP 9195)]
futex_wait_cancelable (private=0, expected=0, futex_word=0x555556de2b60 <renderPool+256>) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
88 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.
(gdb)
As you can see, I'm getting a SIG33, and the program tries to access a file called futex-internal.h that isn't there. I have no experience with debugging at this level, so I wanted to ask here how I could get past this hurdle. The reason I'm trying to get the debugger to work is I'm investigating a strange crash I'm getting with Hideous Destructor that doesn't seem to affect other users.
Hello, I compiled the 4.1.3 release with the Debug flag enabled on Debian Sid according to the guide here [url]https://zdoom.org/wiki/Compile_GZDoom_on_Linux#Debugging[/url]. However, it seems that I'm getting stuck after trying to actually run GZDoom in the debugger tool
[code]ignacio@heim:~/data/gzdoom_build/gzdoom/build$ gdb ./gzdoom
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 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 "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./gzdoom...done.
(gdb) set logging on gzdoomdebug.log
Copying output to gzdoomdebug.log.
(gdb) run
Starting program: /home/ignacio/data/gzdoom_build/gzdoom/build/gzdoom
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff513d700 (LWP 9195)]
GZDoom g4.1.3 - 2019-06-08 07:56:19 -0400 - SDL version
Compiled on Jul 5 2019
Thread 2 "gzdoom" received signal SIG33, Real-time event 33.
[Switching to Thread 0x7ffff513d700 (LWP 9195)]
futex_wait_cancelable (private=0, expected=0, futex_word=0x555556de2b60 <renderPool+256>) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
88 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.
(gdb)
[/code]
As you can see, I'm getting a SIG33, and the program tries to access a file called futex-internal.h that isn't there. I have no experience with debugging at this level, so I wanted to ask here how I could get past this hurdle. The reason I'm trying to get the debugger to work is I'm investigating a strange crash I'm getting with Hideous Destructor that doesn't seem to affect other users.