Bug 2160211

Summary:	Excessive warning: Can't open file […] which was expanded to […] during file-backed mapping note processing
Product:	[Fedora] Fedora	Reporter:	Christian Stadelmann <fedora>
Component:	gdb	Assignee:	Kevin Buettner <kevinb>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	37	CC:	ahajkova, anfreund, blarsen, fweimer, jan, keiths, kevinb, mcermak, pmuldoon, sergiodj
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gdb-13.2-2.fc38 gdb-13.2-2.fc37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-03 01:29:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christian Stadelmann 2023-01-11 19:20:35 UTC

When reporting a bug through ABRT, the backtrace generated by gdb contains the following line more than 100 times:

> warning: Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing

Example backtrace file: See attachment https://bugzilla-attachments.redhat.com/attachment.cgi?id=1915089 for bug #2131093.

Version info (in my case):
gdb-12.1-6.fc37.x86_64
abrt-2.15.1-6.fc37.x86_64
libreport-2.17.4-1.fc37.x86_64
glibc-2.36-8.fc37.x86_64
libgcc-12.2.1-4.fc37.x86_64

This warning happens way too often. Printing it 135 times (in my case) or 148 times (in the attachment linked above) is way more than necessary. Is there any benefit from printing it multiple times? How about printing it only once? This would make it easier to read the backtrace files.

Comment 1 Kevin Buettner 2023-06-19 04:20:18 UTC

This has been fixed upstream by Lancelot SIX in these commits:

0ad504dd464 gdb/corelow.c: avoid repeated warnings in build_file_mappings
ea70f941f9b gdb/corelow.c: do not try to reopen a file if open failed once

I'll retest after the GDB 13.2 backport is finished and, if still present,
I'll backport those changes.

Comment 2 Fedora Update System 2023-07-01 01:52:18 UTC

FEDORA-2023-e7fc561ea9 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e7fc561ea9

Comment 3 Fedora Update System 2023-07-01 02:30:32 UTC

FEDORA-2023-874b5b7697 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-874b5b7697

Comment 4 Fedora Update System 2023-07-02 01:06:04 UTC

FEDORA-2023-874b5b7697 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-874b5b7697`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-874b5b7697

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-07-02 02:12:15 UTC

FEDORA-2023-e7fc561ea9 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e7fc561ea9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e7fc561ea9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-07-03 01:29:04 UTC

FEDORA-2023-e7fc561ea9 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2023-07-17 00:50:14 UTC

FEDORA-2023-874b5b7697 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.