From: Muhammad Umer <umer2834@hotmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.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: Thu, 21 May 2020 05:17:49 +0500 [thread overview]
Message-ID: <SG2PR06MB2951B5135037581427186E04CDB70@SG2PR06MB2951.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20200520143443.GA1621248@host1.jankratochvil.net>
Thank you all for your valuable inputs. I really appreciate it.
On May 20 2020, at 7:34 pm, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> On Wed, 20 May 2020 16:11:43 +0200, Muhammad Umer wrote: > From your statement, I'm assuming the gdb version in RHEL 7.7, is using > debuginfod, and not librpm, right? All Fedora+RHEL releases still use librpm. debuginfod could be expected in RHEL-9+ or some future RHEL-8.y release (but RHEL-8.y maybe not) but nobody knows what will be released in the future. BTW you should always use Developer Toolset GDB on any RHEL. This will provide you more recent GDB release on RHEL. The base RHEL system GDB is there for some compatibility reasons only. Regards, Jan Kratochvil
prev parent reply other threads:[~2020-05-21 0:17 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
2020-05-20 14:11 ` Muhammad Umer
2020-05-20 14:34 ` Jan Kratochvil
2020-05-21 0:17 ` Muhammad Umer [this message]
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=SG2PR06MB2951B5135037581427186E04CDB70@SG2PR06MB2951.apcprd06.prod.outlook.com \
--to=umer2834@hotmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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