Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: patch to display ia64 function pointers
Date: Mon, 25 Aug 2003 21:12:00 -0000	[thread overview]
Message-ID: <1030825211237.ZM7510@localhost.localdomain> (raw)
In-Reply-To: "J. Johnston" <jjohnstn@redhat.com> "RFA: patch to display ia64 function pointers" (Jul 31,  6:01pm)

On Jul 31,  6:01pm, J. Johnston wrote:

> The following patch fixes the problem when displaying structs or function
> pointers that actually point to a function descriptor per the ia64 ABI.
> Currently, the function descriptor pointer is erroneously interpreted as
> pointing to a function and so gdb spits out some meaningless information.
> 
> With the patch, you get to see the actual function that the pointer
> is referencing via the function descriptor.
> 
> Ok to commit?
> 
> 2003-07-31  Jeff Johnston  <jjohnstn@redhat.com>
> 
> 	* ia64-tdep.c (ia64_convert_from_func_addr): New function.
> 	(ia64_gdbarch_init): Call set_gdbarch_convert_from_func_addr().

Okay.

Thanks,

Kevin

P.S. Please let me know if you're waiting on me to review any more of
your patches.


  reply	other threads:[~2003-08-25 21:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 22:01 J. Johnston
2003-08-25 21:12 ` Kevin Buettner [this message]
2003-08-26 17:34   ` J. Johnston
2003-08-26 22:37     ` [patch] missing case in epilogue stub detection Jafa
2003-08-26 22:45       ` Daniel Jacobowitz
2003-08-26 23:01         ` Jafa
2003-09-07 15:16           ` Daniel Jacobowitz
2003-09-09  3:00             ` Andrew Cagney
2003-08-26 19:46 RFA: patch to display ia64 function pointers Michael Elizabeth Chastain

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=1030825211237.ZM7510@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.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