Wind River Support Network

HomeDefectsLIN6-10107
Fixed

LIN6-10107 : Breaking off 1 RPM command gives bogus output for the next

Created: Jun 25, 2015    Updated: Dec 3, 2018
Resolved Date: Jul 7, 2015
Previous ID: LIN6-10062, LIN7-4233
Found In Version: 6.0.0.20
Fix Version: 6.0.0.23
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Userspace

Description

Bogus (?) messages seen such as:

BDB2053 Freeing read locks for locker 0xc: 512/140640001664832

and

BDB2017 Freeing mutex for process: 512/0

when running rpm after interrupting (^C) a previous rpm command.

Steps to Reproduce

$ configure --enable-board=intel-x86-64 --enable-rootfs=glibc_std --enable-kernel=preempt_rt
$ make fs
$ make start-target

Login as root.


# rpm -Va
S.?.....    /bin/busybox.nosuid
....L...    /bin/sh
S.5....T  c /etc/nsswitch.conf
S.5....T  c /etc/shells
.M......    /proc
...
^C

# rpm -Vf /bin/ls
BDB2053 Freeing read locks for locker 0x1: 512/140640001664832
BDB2053 Freeing read locks for locker 0x3: 512/140640001664832
BDB2053 Freeing read locks for locker 0x5: 512/140640001664832
BDB2053 Freeing read locks for locker 0x9: 512/140640001664832
BDB2053 Freeing read locks for locker 0xc: 512/140640001664832
BDB2017 Freeing mutex for process: 512/0
BDB2017 Freeing mutex for process: 512/0
BDB2017 Freeing mutex for process: 512/0
BDB2017 Freeing mutex for process: 512/0
...

Other Downloads


Live chat
Online