* On 5/28/23 18:01, Felix Miata wrote:
Felix Miata composed on 2023-05-28 03:08 (UTC-0400): # zypper ref Segmentation fault (core dumped) # gdb zypper ref GNU gdb (GDB; openSUSE Tumbleweed) 12.1 Copyright (C) 2022 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 "i586-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. 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 zypper... (No debugging symbols found in zypper) /var/cache/zypp/packages/OSS/i586/ref: No such file or directory. Missing separate debuginfos, use: zypper install zypper-debuginfo-1.14.60-1.2.i586 (gdb) run Starting program: /usr/bin/zypper [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb5f54b40 (LWP 986)] [Detaching after fork from child process 987] [New Thread 0xb54ffb40 (LWP 989)]
Usage: [...] [Inferior 1 (process 983) exited normally] (gdb)
Now what?
You'd have to "run ref", not just "run". Additional parameters on the command like (like you've given "zypper ref") to gdb are interpreted differently - namely "ref" as the argument to a core dump image. Arguments for the inferior have to be passed to the "run" command. Mihai