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/24549] [cc-with-gdb-index/cc-with-debug-names] DW_AT_main_subprogram ignored
Date: Fri, 05 Feb 2021 09:56:49 +0000	[thread overview]
Message-ID: <bug-24549-4717-h3tn7ZV6V1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24549-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

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

commit a22ec6e8a4b9006e342ad20c36357a5ba8ba1e74
Author: Tom de Vries <tdevries@suse.de>
Date:   Fri Feb 5 10:56:39 2021 +0100

    [gdb/testsuite] Add KFAILs for PR symtab/24549

    When an executable contains an index such as a .gdb_index or .debug_names
    section, gdb ignores the DW_AT_subprogram attribute.

    This problem has been filed as PR symtab/24549.

    Add KFAILs for this PR in test-cases gdb.dwarf2/main-subprogram.exp and
    gdb.fortran/mixed-lang-stack.exp.

    Tested on x86_64-linux.

    gdb/testsuite/ChangeLog:

    2021-02-05  Tom de Vries  <tdevries@suse.de>

            * gdb.dwarf2/main-subprogram.exp: Add KFAIL for PR symtab/24549.
            * gdb.fortran/mixed-lang-stack.exp: Same.

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

  parent reply	other threads:[~2021-02-05  9:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24549-4717@http.sourceware.org/bugzilla/>
2020-04-17  8:59 ` [Bug gdb/24549] " vries at gcc dot gnu.org
2021-01-29 14:39 ` [Bug symtab/24549] " vries at gcc dot gnu.org
2021-02-05  9:56 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-08 12:09 ` vries at gcc dot gnu.org
2021-02-23 19:01 ` tromey at sourceware dot org
2021-03-28 16:22 ` tromey at sourceware dot org
2023-09-13  7:15 ` vries at gcc dot gnu.org
2023-10-10  8:26 ` cvs-commit at gcc dot gnu.org
2023-12-10 15:21 ` tromey at sourceware dot org
2024-01-10  2:01 ` tromey at sourceware dot org
2024-01-18 20:38 ` cvs-commit at gcc dot gnu.org
2024-01-18 20:38 ` tromey at sourceware dot org
2024-01-18 20:40 ` tromey at sourceware dot org

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-24549-4717-h3tn7ZV6V1@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).