This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
tdep/1357: Mechanism to map address onto arch/mach
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 28 Aug 2003 22:42:00 -0000
- Subject: tdep/1357: Mechanism to map address onto arch/mach
- Reply-to: ac131313 at redhat dot com
>Number: 1357
>Category: tdep
>Synopsis: Mechanism to map address onto arch/mach
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Thu Aug 28 22:48:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
There needs to be a standard interface for mapping an address onto an arch/mach. Several things need this:
- breakpoints
So that "(gdb) break *0x1234" knows what type of memory breakpoint to insert at that point.
- disassembler
So that "(gdb) x/i 0x1234" displays the correct disassembly
Ex: ARM/THUMB, MIPS16/MIPS, sh4/sh5, m68hc11/m68hc12, i386/x86-64, ....
Note though that what ever the mechanism, it should probably be pushed up towards opcodes/ or bfd/. This is because "objdump -d" also requires this facility.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: