This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/550: Investigate making gdbarch_data() initialize on-demand
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 18 May 2002 16:56:55 -0000
- Subject: gdb/550: Investigate making gdbarch_data() initialize on-demand
- Reply-to: ac131313 at redhat dot com
>Number: 550
>Category: gdb
>Synopsis: Investigate making gdbarch_data() initialize on-demand
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sat May 18 09:58:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: 2002-05-18
>Organization:
>Environment:
>Description:
Look at changing the per-architecture data-pointers so that they are initialized on-demand.
At present gdbarch_data() and set_gdbarch_data() get/set the value of the data-pointer. Assuming that these are used to implement on-demand initializatioin of the data-pointer, it can probably be made the default behavour:
get_gdbarch_data() returns the current value.
set_gdbarch_data() sets the current value.
gdbarch_data() If NULL, initializes the data-value. Regardless, returns the data value.
Would need to be careful to detect cycles in such a system (at present they are detected by dumping core :-( ).
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: