From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: bauerman@br.ibm.com (Thiago Jung Bauermann)
Cc: drow@false.org (Daniel Jacobowitz), gdb-patches@sourceware.org
Subject: Re: [rfc/rft] ppc gdbserver: autodetect AltiVec and SPE
Date: Mon, 21 Apr 2008 14:04:00 -0000 [thread overview]
Message-ID: <200804211255.m3LCtQWp029553@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <1208752523.5808.141.camel@localhost.localdomain> from "Thiago Jung Bauermann" at Apr 21, 2008 01:35:23 AM
Thiago Jung Bauermann wrote:
> On Sun, 2008-04-20 at 10:27 -0400, Daniel Jacobowitz wrote:
> > > Is such way of compiling 32-bit GDB in a ppc64 machine with 32-bit
> > > default gcc not supported? Must one always use --target option to
> > > configure in such case?
> >
> > I see. Anything is supported that we're willing to fix... The
> > simplest possible fix would be to add the e500 objects. Does
> > gdbserver work OK with this patch?
>
> Yes, it compiled fine. Thanks!
Sorry for the breakage. My understanding is that building a 32-bit
powerpc64-linux gdbserver was never supported, and would fail at
run time because ptrace does not support accessing 64-bit inferior
registers from a 32-bit debugger (at least not using the standard
ptrace functions).
However, with bi-arch support, I guess it now would actually work
at least for debugging 32-bit inferiors.
I'm wondering whether it wouldn't make sense now to drop the
configure-time distinction between powerpc-linux and powerpc64-linux
for gdbserver (just like there already is no such distinction
for GDB itself).
This would mean no matter whether you configure for powerpc-linux
or for powerpc64-linux, the resulting gdbserver would always support
32-bit inferiors, and would in addition support 64-bit inferiors iff
it was built as a 64-bit executable.
Dan, what do you think?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2008-04-21 12:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 1:11 [rfc][3/3] gdbserver bi-arch for ppc: enable bi-arch support Ulrich Weigand
2008-02-27 13:20 ` Daniel Jacobowitz
2008-02-28 7:16 ` Ulrich Weigand
2008-02-28 14:13 ` Daniel Jacobowitz
2008-02-28 17:03 ` [rfc/rft] ppc gdbserver: autodetect AltiVec and SPE Ulrich Weigand
2008-02-28 17:12 ` Daniel Jacobowitz
2008-03-26 20:21 ` Ulrich Weigand
2008-04-19 0:19 ` Thiago Jung Bauermann
2008-04-19 6:17 ` Daniel Jacobowitz
2008-04-20 14:28 ` Thiago Jung Bauermann
2008-04-21 9:21 ` Daniel Jacobowitz
2008-04-21 10:00 ` Thiago Jung Bauermann
2008-04-21 14:04 ` Ulrich Weigand [this message]
2008-04-21 14:32 ` Daniel Jacobowitz
2008-04-21 15:36 ` Ulrich Weigand
2008-04-21 15:38 ` Daniel Jacobowitz
2008-04-17 17:47 ` Daniel Jacobowitz
2008-04-17 19:03 ` Daniel Jacobowitz
2008-04-17 21:34 ` Ulrich Weigand
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=200804211255.m3LCtQWp029553@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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