diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2025-05-06 16:55:44 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2025-05-06 16:55:44 +0100 |
| commit | 998165ba99a3bcc80ba0b196223f4d49623e87b4 (patch) | |
| tree | d071e8542755c9284dd44ad21f4983d4ec412c0d /gdb/python/python.c | |
| parent | 420d030e88d2c8bbad6044278000fbd9efbf65d9 (diff) | |
| download | binutils-998165ba99a3bcc80ba0b196223f4d49623e87b4.zip binutils-998165ba99a3bcc80ba0b196223f4d49623e87b4.tar.gz binutils-998165ba99a3bcc80ba0b196223f4d49623e87b4.tar.bz2 | |
Revert "gdb: support zero inode in generate-core-file command"
This reverts commit 1e21c846c275fc6e387ca903a129096be2a53d0b.
This change was causing unexpected mappings to be included in the core
files generated by GDB, which was triggering warnings when GDB opened
a core file, like this:
warning: Can't open file [stack] during file-backed mapping note processing
warning: Can't open file [vvar] during file-backed mapping note processing
For now I'm reverting the above commit and will come to the list again
when I have a solution that addresses the original issue without also
including the unexpected mappings.
Diffstat (limited to 'gdb/python/python.c')
0 files changed, 0 insertions, 0 deletions