From: Elena Zannoni <ezannoni@cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com, cagney@cygnus.com
Subject: Re: [RFA] Fix "info func" display for 64-bit minimal symbols
Date: Fri, 11 May 2001 10:40:00 -0000 [thread overview]
Message-ID: <15100.9251.925310.432238@kwikemart.cygnus.com> (raw)
In-Reply-To: <3ADCBA24.74216729@cygnus.com>
Was this checked in?
If not, go ahead.
Thanks
Elena
Michael Snyder writes:
> This is a resubmission of a patch I sent several months ago,
> incorporating feedback.2001-04-17 Michael Snyder <msnyder@redhat.com>
>
> * symtab.c (print_msymbol_info): Allow for 64-bit addresses.
>
> Index: symtab.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/symtab.c,v
> retrieving revision 1.34
> diff -c -3 -p -r1.34 symtab.c
> *** symtab.c 2001/04/01 19:50:50 1.34
> --- symtab.c 2001/04/17 21:45:53
> *************** print_symbol_info (namespace_enum kind,
> *** 2660,2668 ****
> static void
> print_msymbol_info (struct minimal_symbol *msymbol)
> {
> ! printf_filtered (" %08lx %s\n",
> ! (unsigned long) SYMBOL_VALUE_ADDRESS (msymbol),
> ! SYMBOL_SOURCE_NAME (msymbol));
> }
>
> /* This is the guts of the commands "info functions", "info types", and
> --- 2660,2676 ----
> static void
> print_msymbol_info (struct minimal_symbol *msymbol)
> {
> ! char *tmp;
> !
> ! if (TARGET_ADDR_BIT <= 32)
> ! tmp = longest_local_hex_string_custom (SYMBOL_VALUE_ADDRESS (msymbol)
> ! & (CORE_ADDR) 0xffffffff,
> ! "08l");
> ! else
> ! tmp = longest_local_hex_string_custom (SYMBOL_VALUE_ADDRESS (msymbol),
> ! "016l");
> ! printf_filtered ("%s %s\n",
> ! tmp, SYMBOL_SOURCE_NAME (msymbol));
> }
>
> /* This is the guts of the commands "info functions", "info types", and
next parent reply other threads:[~2001-05-11 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ADCBA24.74216729@cygnus.com>
2001-05-11 10:40 ` Elena Zannoni [this message]
2001-05-11 10:48 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15100.9251.925310.432238@kwikemart.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=cagney@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox