You are not logged in.
Basically, gdb is not usable. Whenever I try to run gdb, there it fails with segmentation fault.
~ » gdb -v
[1] 320569 segmentation fault (core dumped) gdb -vThis is the output of coredumpctl:
~ » coredumpctl gdb
PID: 320569 (gdb)
UID: 1000 (<redacted>)
GID: 1000 (<redacted>)
Signal: 11 (SEGV)
Timestamp: Mon 2021-03-15 23:41:25 CET (2min 20s ago)
Command Line: gdb -v
Executable: /usr/local/bin/gdb
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (<redacted>)
Boot ID: 005f04626c5d413987f2aff98bba07cf
Machine ID: de1bc5357bc74d02a9e03d642e977a2a
Hostname: <redacted>
Storage: /var/lib/systemd/coredump/core.gdb.1000.005f04626c5d413987f2aff98bba07cf.320569.1615848085000000.zst
Message: Process 320569 (gdb) of user 1000 dumped core.
Stack trace of thread 320569:
#0 0x00007feb19425755 PyEval_ReleaseLock (libpython3.9.so.1.0 + 0xe3755)
#1 0x0000559383ddd085 do_start_initialization (gdb + 0x36f085)
#2 0x0000559383ee536a _Z20initialize_all_filesv (gdb + 0x47736a)
#3 0x0000559383e92eb6 _Z8gdb_initPc (gdb + 0x424eb6)
#4 0x0000559383d5ea02 captured_main_1 (gdb + 0x2f0a02)
#5 0x0000559383d5f84b captured_main (gdb + 0x2f184b)
#6 0x0000559383b4cf7c main (gdb + 0xdef7c)
#7 0x00007feb18861b25 __libc_start_main (libc.so.6 + 0x27b25)
#8 0x0000559383b5347e _start (gdb + 0xe547e)
gdb terminated by signal SEGV.I would be very grateful if anyone could help with this issue.
Last edited by 3nt3 (2021-03-16 01:47:19)
Offline
Executable: /usr/local/bin/gdb
That's not where Arch installs gdb. Try /usr/bin/gdb and/or ask for help wherever you got that file.
Offline
oh ok, I just removed /usr/local/bin/gdb and now it works. thanks ![]()
Offline