This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/16200] New: Runbing inferior with incompatible architecture lead to crash


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

            Bug ID: 16200
           Summary: Runbing inferior with incompatible architecture lead
                    to crash
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: sanimir.agovic at intel dot com

Selecting an architecture which is not compatible with the target architecture
and running an inferior crashes gdb with an internal error 'bad register size'.
One cannot recover gdb from this error anymore (Recursive internal problem)

NOTE: This requires at least support for two incompatible targets e.g.
--enable-targets=mips,sparc (or all)

$ gdb -batch -ex 'set architecture mips' -ex run /bin/ls

stdout> The target architecture is assumed to be mips
stdout> warning: Selected architecture mips is not compatible with reported
target 
stdout> architecture i386:x86-64
stdout> warning: Architecture rejected target-supplied description
stdout> ../../../gdb/gdb/mips-tdep.c:715: internal-error: bad register size
stdout> A problem internal to GDB has been detected,
stdout> further debugging may prove unreliable.
stdout> Quit this debugging session? (y or n) [answered Y; input not from
terminal]
stdout> ../../../gdb/gdb/mips-tdep.c:715: internal-error: bad register size
stdout> A problem internal to GDB has been detected,
stdout> further debugging may prove unreliable.
stdout> Create a core file of GDB? (y or n) [answered Y; input not from
terminal]
stdout> zsh: abort (core dumped)  gdb -batch -ex 'set architecture mips' -ex
run /bin/ls

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]