This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/392: Swap out current when creating new architecture
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 6 Mar 2002 15:27:49 -0000
- Subject: gdb/392: Swap out current when creating new architecture
- Reply-to: ac131313 at redhat dot com
>Number: 392
>Category: gdb
>Synopsis: Swap out current when creating new architecture
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Mar 06 07:28:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
See the thread:
http://sources.redhat.com/ml/gdb-patches/2001-09/msg00342.html
Code is refering to the previous (in current_gdbarch) architecture assuming that that architecture is the same as the current.
(perhaps the trick is to sort the architecture list passed to XXX_gdbarch_init() by most recent to least recent. That way the XXX_gdbarch_init() function can always find the previous architecture belonging to their family)
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: