This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/476: read_register_bytes -> read_registers(buf, regnum, num_regs)
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 8 Apr 2002 15:20:27 -0000
- Subject: gdb/476: read_register_bytes -> read_registers(buf, regnum, num_regs)
- Reply-to: ac131313 at redhat dot com
>Number: 476
>Category: gdb
>Synopsis: read_register_bytes -> read_registers(buf, regnum, num_regs)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Apr 08 08:28:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: 2002-04-08
>Organization:
>Environment:
>Description:
(I assume everyone knows about the problems of read_register_bytes.)
It is used in several ways:
- to save the raw register buffer during inferior function calls (blockframe.c, ...)
- to extract adjacent registers for things like struct passing (valops.c)
Suggest replacing the second with a new function that returns NR_BYTES starting with register REGNUM and then incrementing REGNUM. It uses get_saved_register() and register_virtual_type() et.al.
Suggest, as an interum step, replacing the first with a regnum iterator that lists the registers to be saved/restored. Default is [0..NUM_REGS).
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: