[Bug gdb/31674] New: [gdb] Problems opening corefile for another architecture

[Bug gdb/31674] New: [gdb] Problems opening corefile for another architecture

[vries at gcc dot gnu.org]

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.

[Bug gdb/31674] [gdb] Problems opening corefile for another architecture

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 15482
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15482&action=edit
tgz file with abort.c, a.out and core file produced on aarch64-linux

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