diff options
| author | Sergio Durigan Junior <sergiodj@redhat.com> | 2019-02-23 10:05:19 -0500 |
|---|---|---|
| committer | Sergio Durigan Junior <sergiodj@redhat.com> | 2019-02-23 10:05:19 -0500 |
| commit | 8a6a85134d78531c6adb72a888844f7cfa3a5c56 (patch) | |
| tree | b000c708c280ff1bc296a8fb6c4a72631f65ecbe /bfd | |
| parent | e0e7d3bd218e50275b4c9c9fbf2d3123c73372a9 (diff) | |
| download | gdb-8a6a85134d78531c6adb72a888844f7cfa3a5c56.zip gdb-8a6a85134d78531c6adb72a888844f7cfa3a5c56.tar.gz gdb-8a6a85134d78531c6adb72a888844f7cfa3a5c56.tar.bz2 | |
Use '--readnever' when invoking GDB from gcore.in
Back when I proposed the '--readnever' feature, I somehow forgot or
decided not to include the bits related to gcore.in in the original
patch. This patch finally updates the gcore script to invoke GDB
using '--readnever'.
We've been carrying this patch on Fedora GDB for quite some time, and
as expected the corefiles generated by gcore on Fedora don't have
problems, which I think is the best indicator that the it's safe to
generate corefiles using '--readnever'.
gdb/ChangeLog:
2019-02-23 Sergio Durigan Junior <sergiodj@redhat.com>
* gcore.in: Add '--readnever' option when invoking GDB.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions