From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Kevin Buettner <kevinb@redhat.com>
Subject: [PATCH 0/4] Non-contiguous address range bug fixes / improvements
Date: Sat, 08 Jun 2019 19:55:00 -0000 [thread overview]
Message-ID: <20190608195434.26512-1-kevinb@redhat.com> (raw)
This four part series fixes some bugs associated with GDB's non-contiguous
address range support.
Kevin Buettner (4):
Prefer symtab symbol over minsym for function names in non-contiguous
blocks
dwarf2-frame.c: Fix FDE processing bug involving non-contiguous ranges
Allow display of negative offsets in print_address_symbolic()
Improve test gdb.dwarf2/dw2-ranges-func.exp
gdb/dwarf2-frame.c | 8 +-
gdb/printcmd.c | 8 +-
gdb/stack.c | 15 +-
...anges-func.c => dw2-ranges-func-hi-cold.c} | 44 +-
.../gdb.dwarf2/dw2-ranges-func-lo-cold.c | 82 +++
gdb/testsuite/gdb.dwarf2/dw2-ranges-func.exp | 694 ++++++++++--------
6 files changed, 505 insertions(+), 346 deletions(-)
rename gdb/testsuite/gdb.dwarf2/{dw2-ranges-func.c => dw2-ranges-func-hi-cold.c} (85%)
create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-ranges-func-lo-cold.c
--
2.21.0
next reply other threads:[~2019-06-08 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 19:55 Kevin Buettner [this message]
2019-06-08 19:55 ` [PATCH 2/4] dwarf2-frame.c: Fix FDE processing bug involving non-contiguous ranges Kevin Buettner
2019-06-21 14:34 ` Pedro Alves
2019-06-08 19:55 ` [PATCH 1/4] Prefer symtab symbol over minsym for function names in non-contiguous blocks Kevin Buettner
2019-06-21 14:26 ` Pedro Alves
2019-06-26 17:30 ` Tom Tromey
2019-07-03 23:16 ` Kevin Buettner
2019-06-08 19:55 ` [PATCH 3/4] Allow display of negative offsets in print_address_symbolic() Kevin Buettner
2019-06-21 14:45 ` Pedro Alves
2019-07-03 23:09 ` Kevin Buettner
2019-07-04 1:06 ` Kevin Buettner
2019-06-08 19:55 ` [PATCH 4/4] Improve test gdb.dwarf2/dw2-ranges-func.exp Kevin Buettner
2019-06-26 17:24 ` [PATCH 0/4] Non-contiguous address range bug fixes / improvements Tom Tromey
2019-07-03 20:10 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190608195434.26512-1-kevinb@redhat.com \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox