From: Muhammad Umer <umer2834@hotmail.com>
To: Simon Marchi <simark@simark.ca>,
Sterling Augustine <saugustine@google.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB locks RPM database
Date: Wed, 20 May 2020 05:04:36 +0000 [thread overview]
Message-ID: <SG2PR06MB29515EB55D73E53C4D428024CDB60@SG2PR06MB2951.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <662b173d-e40b-0f08-fecd-c9df4b3bb51d@simark.ca>
Thank you Simon! This helps a lot.
Hopefully RedHat/Fedora folks can offer more insight.
________________________________
From: Simon Marchi <simark@simark.ca>
Sent: Wednesday, May 20, 2020 7:48:44 AM
To: Sterling Augustine <saugustine@google.com>; Muhammad Umer <umer2834@hotmail.com>
Cc: gdb@sourceware.org <gdb@sourceware.org>
Subject: Re: GDB locks RPM database
On 2020-05-19 9:13 p.m., Sterling Augustine via Gdb wrote:
> On Tue, May 19, 2020 at 6:11 PM Muhammad Umer via Gdb <gdb@sourceware.org>
> wrote:
>
>> But why take a lock? If the purpose is to get info about debug packages,
>> why not just query the package database using rpm command and get the
>> required information? Why is taking a lock necessary?
>>
>
> Simon didn't implement the functionality, so you would have to ask redhat,
> or whomever it was that wrote the code. This is not a part of a normal gdb
> installation.
Indeed. I peeked at the Fedora local patches, and this one seems to implement
that feature, using librpm
https://src.fedoraproject.org/rpms/gdb/blob/master/f/gdb-6.6-buildid-locate-rpm.patch
So it's plausible that librpm takes a lock, and that lock wasn't cleaned up
(perhaps because of crash), but I can't know for sure. Hopefully someone from
Red Hat / Fedora can help more.
Simon
next prev parent reply other threads:[~2020-05-20 5:04 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 [this message]
2020-05-20 9:39 ` Jan Kratochvil
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=SG2PR06MB29515EB55D73E53C4D428024CDB60@SG2PR06MB2951.apcprd06.prod.outlook.com \
--to=umer2834@hotmail.com \
--cc=gdb@sourceware.org \
--cc=saugustine@google.com \
--cc=simark@simark.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).