[opensuse-buildservice] Coredump during obs build
Hello, while trying to local build this package: https://build.opensuse.org/package/ show/home:frank_kunz:branches:Base:System/u-boot-sinovoipbpim2plus osc build openSUSE_Factory_ARM armv7l ... [ 33s] initializing rpm db... [ 34s] /usr/lib/build/build-pkg-rpm: line 25: 1647 Illegal instruction (core dumped) chroot $BUILD_ROOT /usr/bin/rpmdb --initdb my build host is: cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20170924" ID=opensuse ID_LIKE="suse" VERSION_ID="20170924" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20170924" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" uname -a Linux pluto 4.13.3-1-default #1 SMP PREEMPT Wed Sep 20 06:43:24 UTC 2017 (76ecbd3) armv7l armv7l armv7l GNU/Linux how can I find out why rpmdb crashes in the buildroot? Br, Frank -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sep 25 2017, Frank Kunz
how can I find out why rpmdb crashes in the buildroot?
Can you inspect the core dump? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 26. September 2017, 09:07:07 CEST schrieb Andreas Schwab:
On Sep 25 2017, Frank Kunz
wrote: how can I find out why rpmdb crashes in the buildroot?
Can you inspect the core dump?
Unfortunately not. A "coredumpctl gdb" generates a new coredump for gdb. I think I need a cross gdb to analyze it on my x86_64 machine. Br, Frank -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sep 26 2017, Frank Kunz
Am Dienstag, 26. September 2017, 09:07:07 CEST schrieb Andreas Schwab:
On Sep 25 2017, Frank Kunz
wrote: how can I find out why rpmdb crashes in the buildroot?
Can you inspect the core dump?
Unfortunately not. A "coredumpctl gdb" generates a new coredump for gdb.
You don't need to run gdb in the chroot. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 26. September 2017, 17:36:36 CEST schrieb Andreas Schwab:
On Sep 26 2017, Frank Kunz
wrote: Am Dienstag, 26. September 2017, 09:07:07 CEST schrieb Andreas Schwab:
On Sep 25 2017, Frank Kunz
wrote: how can I find out why rpmdb crashes in the buildroot?
Can you inspect the core dump?
Unfortunately not. A "coredumpctl gdb" generates a new coredump for gdb.
You don't need to run gdb in the chroot.
So when I try as normal user (which is in the systemd-coredump and systemd- journal groups): coredumpctl gdb PID: 1686 (rpmdb) UID: 0 (root) GID: 0 (root) Signal: 4 (ILL) Timestamp: Mon 2017-09-25 20:21:54 CEST (21h ago) Command Line: /usr/bin/rpmdb --initdb Executable: /home/frank/obs/tmp/build-root/usr/bin/rpmdb Control Group: /user.slice/user-1000.slice/session-c1.scope Unit: session-c1.scope Slice: user-1000.slice Session: c1 Owner UID: 1000 (frank) Boot ID: f50e58c3e3fc4a2283b655e23aaa4144 Machine ID: 369f397622bc58a5577f4bdc59c89670 Hostname: pluto Storage: /var/lib/systemd/coredump/core.rpmdb. 0.f50e58c3e3fc4a2283b655e23aaa4144.1686.1506363714000000.lz4 (inaccessible) Message: Process 1686 (rpmdb) of user 0 dumped core. File "/var/lib/systemd/coredump/core.rpmdb. 0.f50e58c3e3fc4a2283b655e23aaa4144.1686.1506363714000000.lz4" is not readable: Keine Berech tigung When I try as root: coredumpctl gdb PID: 1686 (rpmdb) UID: 0 (root) GID: 0 (root) Signal: 4 (ILL) Timestamp: Mon 2017-09-25 20:21:54 CEST (21h ago) Command Line: /usr/bin/rpmdb --initdb Executable: /home/frank/obs/tmp/build-root/usr/bin/rpmdb Control Group: /user.slice/user-1000.slice/session-c1.scope Unit: session-c1.scope Slice: user-1000.slice Session: c1 Owner UID: 1000 (frank) Boot ID: f50e58c3e3fc4a2283b655e23aaa4144 Machine ID: 369f397622bc58a5577f4bdc59c89670 Hostname: pluto Storage: /var/lib/systemd/coredump/core.rpmdb. 0.f50e58c3e3fc4a2283b655e23aaa4144.1686.1506363714000000.lz4 Message: Process 1686 (rpmdb) of user 0 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 8.0 Copyright (C) 2017 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 "armv7hl-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"... then I come back to the command prompt and coredumpctl lists a further dump: coredumpctl TIME PID UID GID SIG COREFILE EXE Mon 2017-09-25 20:21:55 CEST 1686 0 0 4 present /home/frank/obs/ tmp/build-root/usr/bin/rpmdb Tue 2017-09-26 17:30:02 CEST 4428 0 0 4 present /usr/bin/gdb I will try to copy the /var/lib/systemd/coredump/core.rpmdb. 0.f50e58c3e3fc4a2283b655e23aaa4144.1686.1506363714000000.lz4 to an other machine (with different archirecture) and try to analyze it with gdb. Br, Frank -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 26. September 2017, 17:59:16 CEST schrieb Frank Kunz:
Can you inspect the core dump?
Unfortunately not. A "coredumpctl gdb" generates a new coredump for gdb.
You don't need to run gdb in the chroot.
snip
I will try to copy the /var/lib/systemd/coredump/core.rpmdb. 0.f50e58c3e3fc4a2283b655e23aaa4144.1686.1506363714000000.lz4 to an other machine (with different archirecture) and try to analyze it with gdb.
This is what I have so far:
#0 glob_in_dir (pattern=0x11ed62 ".rpmrc", directory=0x7
After a "zypper dup --no-allow-vendor-change" the problem is gone. Br, Frank -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Andreas Schwab
-
Frank Kunz