From: Simon Marchi <simark@simark.ca>
To: Jan Vrany <jan.vrany@labware.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: skip objfiles with no BFD in DWARF unwinder
Date: Wed, 7 Dec 2022 11:07:12 -0500 [thread overview]
Message-ID: <4d4952bf-0e70-253f-578d-8bdeec8bfafc@simark.ca> (raw)
In-Reply-To: <20220406185524.30713-1-jan.vrany@labware.com>
On 4/6/22 14:55, Jan Vrany via Gdb-patches wrote:
> Changes since v1:
>
> * use with_test_prefix as Lancelot suggested
> * rewrote test as Pedro suggested
> * updated commit message
>
> -- >8 --
> While playing with JIT reader I experienced GDB to crash on null-pointer
> dereference when stepping through non-jitted code.
>
> The problem was that dwarf2_frame_find_fde () assumed that all objfiles
> have BFD but that's not always true. To address this problem, this
> commit skips such objfiles.
>
> To test the fix we put breakpoint in jit_function_add (). The JIT reader
> does not know how unwind this function so unwinding eventually falls
> back to DWARF unwinder which in turn iterates over objfiles. Since the
> the code is jitted, it is guaranteed it would eventually process JIT
> objfile.
> ---
> gdb/dwarf2/frame.c | 3 +++
> gdb/objfiles.h | 4 +++-
> gdb/testsuite/gdb.base/jit-reader.exp | 13 +++++++++++++
> 3 files changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/dwarf2/frame.c b/gdb/dwarf2/frame.c
> index 5878d72f922..514ae8c694f 100644
> --- a/gdb/dwarf2/frame.c
> +++ b/gdb/dwarf2/frame.c
> @@ -1565,6 +1565,9 @@ dwarf2_frame_find_fde (CORE_ADDR *pc, dwarf2_per_objfile **out_per_objfile)
> CORE_ADDR offset;
> CORE_ADDR seek_pc;
>
> + if (objfile->obfd == nullptr)
> + continue;
> +
> comp_unit *unit = find_comp_unit (objfile);
> if (unit == NULL)
> {
> diff --git a/gdb/objfiles.h b/gdb/objfiles.h
> index 8bd76705688..429dea1da4c 100644
> --- a/gdb/objfiles.h
> +++ b/gdb/objfiles.h
> @@ -636,7 +636,9 @@ struct objfile
> struct compunit_symtab *compunit_symtabs = nullptr;
>
> /* The object file's BFD. Can be null if the objfile contains only
> - minimal symbols, e.g. the run time common symbols for SunOS4. */
> + minimal symbols (e.g. the run time common symbols for SunOS4) or
> + if the objfile is a dynamic objfile (e.g. created by JIT reader
> + API). */
>
> bfd *obfd;
>
> diff --git a/gdb/testsuite/gdb.base/jit-reader.exp b/gdb/testsuite/gdb.base/jit-reader.exp
> index d94360cd7d9..756b400906c 100644
> --- a/gdb/testsuite/gdb.base/jit-reader.exp
> +++ b/gdb/testsuite/gdb.base/jit-reader.exp
> @@ -271,6 +271,19 @@ proc jit_reader_test {} {
> "#1 ${any} in main ${any}" \
> ]
> }
> +
> + with_test_prefix "test dwarf unwinder" {
> + # Check that the DWARF unwinder does not crash in presence of
> + # JIT objfiles.
> + gdb_test "up"
> + gdb_breakpoint "*function_add" temporary
> + gdb_test "cont" ".*Temporary breakpoint ${any} in jit_function_add .*"
> + gdb_test "bt" \
> + [multi_line \
> + "#0 ${any} in jit_function_add ${any}" \
> + "#1 ${any} in main ${any}" \
> + ]
> + }
This test function is getting a tad long. In general, I find that it
makes it difficult to know if some part of the test depends on the state
left by a previous portion of the test, if adding something in the
middle will break something later (or silently make a test not test what
it intended to test anymore). I therefore like to split things up in
small independent functions that each start with a clean GDB.
This still LGTM though, not a blocker, but I thought I'd mention it for
future changes.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
prev parent reply other threads:[~2022-12-07 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 10:04 [PATCH] " Jan Vrany
2022-04-05 14:19 ` Lancelot SIX
2022-04-05 14:46 ` Simon Marchi
2022-04-06 17:50 ` Jan Vrany
2022-04-05 19:08 ` Pedro Alves
2022-04-06 18:06 ` Jan Vrany
2022-04-06 18:55 ` [PATCH v2] " Jan Vrany
2022-12-07 11:07 ` Jan Vraný
2022-12-07 16:07 ` Simon Marchi [this message]
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=4d4952bf-0e70-253f-578d-8bdeec8bfafc@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=jan.vrany@labware.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).