This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1399: trad_frame interface exposes internal state codings
- From: rearnsha at arm dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 27 Sep 2003 16:04:12 -0000
- Subject: gdb/1399: trad_frame interface exposes internal state codings
- Reply-to: rearnsha at arm dot com
>Number: 1399
>Category: gdb
>Synopsis: trad_frame interface exposes internal state codings
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Sat Sep 27 16:08:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Richard Earnshaw
>Release: 6.0
>Organization:
>Environment:
All
>Description:
> PS Andrew,
>
> We seem to be horribly overloading and then exposing these special values
> in the trad_frame interface. Wouldn't it make more sense to add more
> routines to get and update the values, then we can hide the special
> meanings entirely (and maybe even change the way they are recorded if we
> need to).
Yes. The last iteration of that added frame_p. Can you leave a
dropping somewhere (either a comment in trad_frame*) or a bug report
pointing this out.
Andrew
http://sources.redhat.com/ml/gdb-patches/2003-09/msg00584.html
>How-To-Repeat:
>Fix:
Provide a more complete set of access routines and then make the trad_frame register structure opaque.
>Release-Note:
>Audit-Trail:
>Unformatted: