[Bug corefiles/18187] New: gdb needs to write first page of segment to core file, even for unmodified segments

[Bug corefiles/18187] New: gdb needs to write first page of segment to core file, even for unmodified segments

[dje at google dot com]

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

            Bug ID: 18187
           Summary: gdb needs to write first page of segment to core file,
                    even for unmodified segments
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: corefiles
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

It's useful to record the contents of .note.gnu.build-id in core files,
e.g., to verify with the corresponding executable.

Currently gdb will skip writing readonly segments that it detects as being
unmodified.

While it's potentially impossible to find where .note.gnu.build-id lives,
a good heuristic is to just write the first (4K) page.

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

[Bug corefiles/18187] gdb needs to write first page of segment to core file, even for unmodified segments

[sergiodj at redhat dot com]

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

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sergiodj at redhat dot com

--- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
I pushed a patch (a few hours after you opened this bug) that completely
rewrites the way GDB deals with corefile generation.  Take a look at Bug 16092.
 Now GDB does not blindly skips readonly segments; it respects the value of
/proc/PID/coredump_filter which can be modified to make it dump segments that
were not being dumped before.  I think this can help in this situation.

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