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: Thu, 11 Mar 2004 19:30:00 -0000 [thread overview]
Message-ID: <4050BE28.3020100@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403101953470.29872@lazy>
> Andrew,
>
>
>>> You'll need a very recent GDB (which contains fixes for the can't insert
>>> breakpoint problem you noticed) a long with these fixes:
>>> http://sources.redhat.com/ml/gdb-patches/2004-03/msg00177.html
>>> http://sources.redhat.com/ml/gdb-patches/2004-03/msg00176.html
>>> which make GDB's handling of register sets more robust.
>
>
> Are these patches valid for gdb 6.1 as well?? or does gdb6.1 take care of
> these problems? I tried these patches on a 6.1 tree and seems like I am
> missing something... I get an ppc-linux-tdep.c:1046: error:
> `ppc32_linux_gregset' undeclared (first use in this function)
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;
Andrew
next prev parent reply other threads:[~2004-03-11 19:30 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 [this message]
2004-03-11 20:30 ` Manoj Iyer
2004-03-12 22:00 ` 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=4050BE28.3020100@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