[Bug corefiles/30126] New: Overly verbose "Can't open file [shared memory path] during file-backed mapping note processing" warnings

["andres at anarazel dot de" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30126

            Bug ID: 30126
           Summary: Overly verbose "Can't open file [shared memory path]
                    during file-backed mapping note processing" warnings
           Product: gdb
           Version: 13.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: corefiles
          Assignee: unassigned at sourceware dot org
          Reporter: andres at anarazel dot de
  Target Milestone: ---

Hi, 

Whenever loading a core dump from postgres, I'm greeted by a series of warnings
like this:

warning: Can't open file /anon_hugepage (deleted) during file-backed mapping
note processing
warning: Can't open file /dev/shm/PostgreSQL.1150234652 during file-backed
mapping note processing
warning: Can't open file /dev/shm/PostgreSQL.535700290 during file-backed
mapping note processing
warning: Can't open file /SYSV604b7d00 (deleted) during file-backed mapping
note processing

Sometimes hundreds of such notes will be emitted, because of shorter lived
shared memory allocations.

None of those files will ever exist, and that's OK.

Unfortunately the above warnings can't be quieted by any setting as far as I
can see.


From what I can tell the core dump unfortunately does not contain information
that'd allow to distinguish the above automatically from other "real" files. So
I don't really have a better idea than to quiesce those warnings than to do
string prefix matching.

Looks like there's already some code for this in gdb, in
gdb/linux-tdep.c:mapping_is_anonymous_p, but it's not used for weeding out
files during core dump load.

Regards,

Andres

-- 
You are receiving this mail because:
You are on the CC list for the bug.