public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/25807] [readnow] FAIL: gdb.threads/tls.exp: print a_thread_local
Date: Thu, 24 Apr 2025 16:57:40 +0000	[thread overview]
Message-ID: <bug-25807-4717-GhM8srbBKi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25807-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kevin Buettner <kevinb@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8b87fe90e81f933b7c88e1ea25b02426ee3f58eb

commit 8b87fe90e81f933b7c88e1ea25b02426ee3f58eb
Author: Kevin Buettner <kevinb@redhat.com>
Date:   Wed Apr 23 21:39:28 2025 -0700

    Don't attempt to find TLS address when target has no registers

    This commit fixes two bugs, one of which is Bug 25807, which occurs
    when target_translate_tls_address() is called from
    language_defn::read_var_value in findvar.c.  I found it while testing on
    aarch64; it turned a KFAIL for gdb.threads/tls.exp: print a_thread_local
    into a FAIL due to a GDB internal error.  Now, with this commit in place,
    the KFAIL/FAIL turns into a PASS.

    In addition to the existing test just noted, I've also added a test to
    the new test case gdb.base/tls-nothreads.exp.  It'll be tested, using
    different scenarios, up to 8 times:

    PASS: gdb.base/tls-nothreads.exp: default: force_internal_tls=false: after
exit: print tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: default: force_internal_tls=true: after
exit: print tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: static: force_internal_tls=false: after
exit: print tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: static: force_internal_tls=true: after
exit: print tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads: force_internal_tls=false: after
exit: print tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads: force_internal_tls=true: after
exit: print tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads-static:
force_internal_tls=false: after exit: print tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads-static: force_internal_tls=true:
after exit: print tls_tbss_1

    There is a related problem that occurs when target_translate_tls_address
    is called from find_minsym_type_and_address() in minsyms.c.  It can be
    observed when debugging a program without debugging symbols when the
    program is not executing.  I've written a new test for this, but it's
    (also) included in the new test case gdb.base/tls-nothreads.exp, found
    later in this series.  Depending on the target, it can run up to 8
    times using different scenarios.  E.g., on aarch64, I'm seeing these
    PASSes, all of which test this change:

    PASS: gdb.base/tls-nothreads.exp: default: force_internal_tls=false:
stripped: after exit: print (int) tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: default: force_internal_tls=true:
stripped: after exit: print (int) tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: static: force_internal_tls=false:
stripped: after exit: print (int) tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: static: force_internal_tls=true:
stripped: after exit: print (int) tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads: force_internal_tls=false:
stripped: after exit: print (int) tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads: force_internal_tls=true:
stripped: after exit: print (int) tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads-static:
force_internal_tls=false: stripped: after exit: print (int) tls_tbss_1
    PASS: gdb.base/tls-nothreads.exp: pthreads-static: force_internal_tls=true:
stripped: after exit: print (int) tls_tbss_1

    In an earlier version of this commit (v4), I was checking whether the
    target has registers in language_defn::read_var_value in findvar.c and
    in find_minsym_type_and_address in minsyms.c, printing suitable error
    messages in each case.  In his review of this commit for the v4
    series, Tom Tromey asked whether it would be better to do this check
    in target_translate_tls_address.  I had considered doing that for the
    v4 (and earlier) series, but I wanted to print slightly different
    messages at each check.  Also, read_var_value in findvar.c was already
    printing a message in some cases and I had arranged for the later
    check in that function to match the original message.

    However, while I had added a target-has-registers check at two of the
    call sites for target_translate_tls_address, I hadn't added it at the
    third call site which is in dwarf_expr_context::execute_stack_op() in
    dwarf2/expr.c.  I believe that in most cases, this is handled by the
    early check in language_defn::read_var_value...

      else if (sym_need == SYMBOL_NEEDS_REGISTERS && !target_has_registers ())
        error (_("Cannot read `%s' without registers"), var->print_name ());

    ...but it's entirely possible that dwarf_expr_context::execute_stack_op()
    might get called in some other context.  So it makes sense to do the
    target-has-registers check for that case too.  And rather than add yet
    another check at that call site, I decided that moving the check and
    error message to target_translate_tls_address makes sense.

    I had to make the error messages that it prints somewhat more generic.
    In particular, when called from language_defn::read_var_value, the
    message printed by target_translate_tls_address no longer matches the
    earlier message that could be printed (as shown above).  That meant
    that the test cases which check for this message, gdb.threads/tls.exp,
    and gdb.base/tls-nothreads.exp had to be adjusted to account for the
    new message.  Also, I think it's valuable to the user to know (if
    possible) the name of the variable that caused the error, so I've
    added an optional parameter to target_translate_tls_address, providing
    the name of the variable, if it's known.  Therefore, the message
    that's printed when the target-has-registers test fails is one of the
    following:

    When the TLS variable isn't known (due to being called from
    dwarf_expr_context::execute_stack_op):

        "Cannot translate TLS address without registers"

    When the TLS variable is known (from either of the other two call sites
    for target_translate_tls_address):

        "Cannot find address of TLS symbol `%s' without registers"

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=25807
    Tested-By: Luis Machado <luis.machado@arm.com>
    Approved-By: Luis Machado <luis.machado@arm.com>

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

      parent reply	other threads:[~2025-04-24 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 11:52 [Bug symtab/25807] New: " vries at gcc dot gnu.org
2020-04-09 11:57 ` [Bug symtab/25807] " vries at gcc dot gnu.org
2020-04-09 14:31 ` vries at gcc dot gnu.org
2020-04-23 13:42 ` cvs-commit at gcc dot gnu.org
2024-01-26 13:59 ` ssbssa at sourceware dot org
2025-04-24 16:57 ` cvs-commit at gcc dot gnu.org [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=bug-25807-4717-GhM8srbBKi@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).