From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/rfc:ppc] svr4 and not just ELFOSABI_LINUX for function parsing et.al.
Date: Mon, 22 Apr 2002 00:59:00 -0000 [thread overview]
Message-ID: <1020422075910.ZM32309@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@cygnus.com> "[rfa/rfc:ppc] svr4 and not just ELFOSABI_LINUX for function parsing et.al." (Apr 22, 12:29am)
On Apr 22, 12:29am, Andrew Cagney wrote:
> I was finding that for a non-GNU/Linux SVR4 PPC platform malloc() was
> failing because RS6000 TOC func-ptr code was being selected:
>
> /* Handle RS/6000 function pointers. */
> set_gdbarch_convert_from_func_ptr_addr (gdbarch,
> rs6000_convert_from_func_ptr_addr);
>
> the attached patch changes things to select all of:
>
> set_gdbarch_frameless_function_invocation (gdbarch,
> ppc_linux_frameless_function_invocation);
> set_gdbarch_frame_chain (gdbarch, ppc_linux_frame_chain);
> set_gdbarch_frame_saved_pc (gdbarch, ppc_linux_frame_saved_pc);
>
> set_gdbarch_frame_init_saved_regs (gdbarch,
> ppc_linux_frame_init_saved_regs);
> set_gdbarch_init_extra_frame_info (gdbarch,
> ppc_linux_init_extra_frame_info);
>
> set_gdbarch_memory_remove_breakpoint (gdbarch,
>
> ppc_linux_memory_remove_breakpoint);
> set_solib_svr4_fetch_link_map_offsets
> (gdbarch, ppc_linux_svr4_fetch_link_map_offsets);
>
> when svr4_abi. It certainly improves things (fails went from 136 -> 80)
> but I'm not 100% certain if this is correct for all the above - I
> suspect it is overkill :-/
It looks okay to me. I have no problem with you checking it in.
Kevin
next prev parent reply other threads:[~2002-04-22 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 21:29 Andrew Cagney
2002-04-22 0:59 ` Kevin Buettner [this message]
2002-04-25 21:31 ` Andrew Cagney
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=1020422075910.ZM32309@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.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