On 2023-05-28 18:39, Felix Miata wrote:
Mihai Moldovan composed on 2023-05-28 18:18 (UTC+0200):
* On 5/28/23 18:01, Felix Miata wrote:
...
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.
Thanks!
Would what follows be enough new bug report? (gdb) run dup Starting program: /usr/bin/zypper dup [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb5f54b40 (LWP 1291)]
...
[Detaching after fork from child process 1316]
Thread 1 "Zypp-main" received signal SIGSEGV, Segmentation fault. 0xb48bc70f in ?? () from /lib/libjavascriptcoregtk-4.0.so.18 Missing separate debuginfos, use: zypper install libblkid1-debuginfo-2.38.1-13.1.i586 libffi8-debuginfo-3.4.4-1.7.i586 libgio-2_0-0-debuginfo-2.76.3-1.1.i586 libgmodule-2_0-0-debuginfo-2.76.3-1.1.i586 libgobject-2_0-0-debuginfo-2.76.3-1.1.i586 libicu72-debuginfo-72.1-2.3.i586 liblz4-1-debuginfo-1.9.4-2.3.i586 libproxy1-pacrunner-webkit-debuginfo-0.4.18-1.5.i586 libsystemd0-debuginfo-253.4-2.1.i586
Notice that at this point you would normally run that "zypper install ..." command to install the debug packages, so that the information given by gdb is complete on a new run — but this time you can not do that. Simon Lees posted a bugzilla report for you to see. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)