public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31674] New: [gdb] Problems opening corefile for another architecture
Date: Tue, 23 Apr 2024 15:50:49 +0000	[thread overview]
Message-ID: <bug-31674-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31674
           Summary: [gdb] Problems opening corefile for another
                    architecture
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

This is tentative at this point.

I came across the use case of gdb opening a corefile for another architecture
than the native one.

This script ( https://github.com/malyzelenyhnus/gdb-setupcore ) reports (for
the early days of debuginfod support in gdb) a problem for this use case where
gdb ends up using native files somehow.

This may be:
- a bug in current gdb, or 
- a fixed bug in current gdb, or
- improper use of gdb, or 
- the supported way of getting this work.

I'm not sure which one it is, but I'd like to find out.

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

             reply	other threads:[~2024-04-23 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 15:50 vries at gcc dot gnu.org [this message]
2024-04-29  8:34 ` [Bug gdb/31674] " vries at gcc dot gnu.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-31674-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).