From: Andrew Cagney <cagney@gnu.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: (PPC64) 64 bit GDB unable to set br in 32bit app
Date: Fri, 12 Mar 2004 22:00:00 -0000 [thread overview]
Message-ID: <4052331A.5000508@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403112055260.22962@lazy>
> On Thu, 11 Mar 2004, Andrew Cagney wrote:
>
>
>>>
>>> They are mainline patches that may get backported to 6.1. I'm wondering
>>> if the patches applied cleanly as they appear to contain:
>>>
>>> +static struct regset ppc32_linux_gregset = {
>>> + NULL, ppc32_linux_supply_gregset
>>> +};
>>> ...
>>> +ppc_linux_regset_from_core_section (struct gdbarch *core_arch,
>>> + const char *sect_name, size_t sect_size)
>>> ...
>>> + if (tdep->wordsize == 4)
>>> + return &ppc32_linux_gregset;
>>>
>
>
> No some of them did not, I had to hand edit the code by looking at the
> patch.
It sounds like a problem with the hand editing then - per the above the
variable does appear to have been added.
Andrew
prev parent reply other threads:[~2004-03-12 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 5:55 Manoj Iyer
2004-03-09 20:03 ` Andrew Cagney
2004-03-10 19:28 ` Manoj Iyer
2004-03-11 19:30 ` Andrew Cagney
2004-03-11 20:30 ` Manoj Iyer
2004-03-12 22:00 ` Andrew Cagney [this message]
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=4052331A.5000508@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.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