public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gbenson at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26909] New: [meta] Debug Clang-built code
Date: Tue, 17 Nov 2020 09:49:54 +0000	[thread overview]
Message-ID: <bug-26909-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26909
           Summary: [meta] Debug Clang-built code
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: gbenson at redhat dot com
  Target Milestone: ---

Meta-bug tracking issues relating to debugging code built with using Clang

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

             reply	other threads:[~2020-11-17  9:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  9:49 gbenson at redhat dot com [this message]
2020-11-17  9:51 ` [Bug gdb/26909] " gbenson at redhat dot com
2020-11-17  9:51 ` gbenson at redhat dot com
2020-11-30 12:53 ` vries at gcc dot gnu.org
2022-04-08  0:07 ` tromey at sourceware dot org
2022-05-31 20:53 ` dblaikie at gmail dot com
2022-05-31 20:54 ` dblaikie at gmail dot com
2023-01-04  1:44 ` tromey at sourceware dot org
2023-01-14 19:40 ` tromey at sourceware dot org
2023-03-31 16:56 ` tromey at sourceware dot org
2023-03-31 17:04 ` tromey at sourceware dot org
2023-04-13 12:21 ` tromey at sourceware dot org
2023-04-13 15:01 ` hluaw at connect dot ust.hk
2023-05-11 21:49 ` tromey at sourceware dot org
2023-05-15 15:17 ` 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-26909-4717@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).