This is the mail archive of the gdb@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]

Re: Consistent format for memory addresses


On Thu, May 26, 2005 at 09:11:09AM +1200, Nick Roberts wrote:
> Eli Zaretskii writes:
>  > > From: Nick Roberts <nickrob@snap.net.nz>
>  > > Date: Wed, 25 May 2005 15:52:47 +1200
>  > > Cc: gdb@sources.redhat.com
>  > > 
>  > > In truth I don't mind seven or eight digits. What makes it difficult for me
>  > > is if the output of the CLI commands constantly change.
>  > 
>  > But this (and similar) changes should not be very hard to accommodate
>  > for in Emacs, even if you search for the address as a string.  For
>  > instance, you could use a regexp that allows for an arbitrary number
>  > of leading zeroes, right?
>  > 
>  > Or am I missing something?
> 
> Sure all differences can be accommodated if I know what the rules are. But as
> Mark pointed out there are different systems. Presumably they might have
> different rules. However, if the same function is used to print out all the
> addresses, I don't need to know what format the address has. Since the output
> address the two commands would be identical, I can simply record it from one
> command and look for it in the other.

You know it's a number - it's going to stay a number.  A function to
turn one hex number into a regular expression that would match it with
leading zeros wouldn't be much work.

> The discrepancy in the example I referred to arises because disassemble now
> uses ui_out_field_core_addr while "info frame" still uses
> deprecated_print_address_numeric. The deprecated prefix suggests that this
> arrangement is not permanent. I would like to make changes now like the one
> below. Clearly it would be sensible to change the other calls to
> deprecated_print_address_numeric and, as it stands, it probably introduces a
> memory leak and it might conflict with MI. However, I would like some
> re-assurance that such a change would be accepted before going to the trouble
> of providing a proper patch.

The change is not correct.  The ui_out_* output is considerably different in MI
mode.  I think paddr_nz will do what you want though.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


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