From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Muhammad Umer <umer2834@hotmail.com>
Cc: Simon Marchi <simark@simark.ca>,
Sterling Augustine <saugustine@google.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB locks RPM database
Date: Wed, 20 May 2020 11:39:03 +0200 [thread overview]
Message-ID: <20200520093903.GA1549168@host1.jankratochvil.net> (raw)
In-Reply-To: <SG2PR06MB29515EB55D73E53C4D428024CDB60@SG2PR06MB2951.apcprd06.prod.outlook.com>
On Wed, 20 May 2020 07:04:36 +0200, Muhammad Umer via Gdb wrote:
> Hopefully RedHat/Fedora folks can offer more insight.
I wrote the patch in 2008 using librpm:
https://src.fedoraproject.org/rpms/gdb/c/6a80c39af8f12a670c2dc194674a246fe1ded687
I am not aware of such stale locks but then sometimes rpmdb stale locks could
happen even without any GDB involved and 'rpm --rebuilddb' helps in such case
(or just 'rm -f /var/lib/rpm/_*' but I am not sure how safe it is).
Hopefully it is no longer happening in new RHELs, I do not see it new Fedoras.
Anyway this is really unrelated to upstream GDB and such issues should be
filed through your RHEL support contact.
Still the librpm support is deprecated and no longer being developed as it is
being replaced by debuginfod support which already landed to upstream GDB.
Regards,
Jan Kratochvil
next prev parent reply other threads:[~2020-05-20 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SG2PR06MB29510548426E2177D7C7BAAFCDB90@SG2PR06MB2951.apcprd06.prod.outlook.com>
2020-05-20 0:28 ` Simon Marchi
2020-05-20 1:11 ` Muhammad Umer
2020-05-20 1:13 ` Sterling Augustine
2020-05-20 2:48 ` Simon Marchi
2020-05-20 5:04 ` Muhammad Umer
2020-05-20 9:39 ` Jan Kratochvil [this message]
2020-05-20 14:11 ` Muhammad Umer
2020-05-20 14:34 ` Jan Kratochvil
2020-05-21 0:17 ` Muhammad Umer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200520093903.GA1549168@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=saugustine@google.com \
--cc=simark@simark.ca \
--cc=umer2834@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox