This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdb/494: MI: parse_and_eval_address() -> string_to_core_addr()



>Number:         494
>Category:       gdb
>Synopsis:       MI: parse_and_eval_address() -> string_to_core_addr()
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 17 07:58:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2002-04-17
>Organization:
>Environment:

>Description:
The MI client passes frame addresses to GDB as part of the varobj family of commands.

GDB's MI code then uses parse_and_eval_address() to parse the text value into a CORE_ADDR.  Unfortunatly (as the Insight developers can explain in full detaill), this is wrong.  parse_and_eval_address() is for parsing a pointer into an address.  The operation address->address doesn't work on all architectures.

The ``correct fix'' is to use the recently added function:
  string_to_core_addr()

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]