From: "Anmol P. Paralkar" <b07584@freescale.com>
To: gdb@sourceware.org
Subject: RE: Need advice on building GDB for a large number of PowerPC variants.
Date: Fri, 18 May 2007 13:51:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0705180843520.4318@ld0159-tx32.am.freescale.net> (raw)
In-Reply-To: <655C3D4066B7954481633935A40BB36F041300@ussunex02.svl.access-company.com>
Hello,
Forwarding Michael Snyder's affirmation below. (For some reason, his
response bounced off the mailing list server). Someone else might
need to benefit from this, hence the forward.
Best Regards,
Anmol.
On Thu, 17 May 2007, Michael Snyder wrote:
> Hi Anmol,
>
> You're perfectly correct -- in fact, you might be even luckier in that
> in most respects, a native (ppc-linux) gdb should be able to support
> "target remote". I can't immediately think of anything that should
> prevent debugging both remote and native programs with the same gdb.
>
> Hope you're well,
> Michael
>
>
> -----Original Message-----
> From: gdb-owner@sourceware.org on behalf of Anmol P. Paralkar
> Sent: Thu 5/17/2007 2:43 PM
> To: gdb@sourceware.org
> Subject: Need advice on building GDB for a large number of PowerPC variants.
>
> Hello,
>
> I need to build GDB for a debugging a variety of PowerPC families.
> The host environment is x86 plus a small subset of the PowerPC
> variants. GDB will be used native as well as cross (remote) from
> each host (x86 (cross-only) as well as PowerPC). A substantial
> number of PowerPC flavours is desired to be targetted - the number
> of families and the instances within each family all result in a
> fairly large number of individual targets. Both the variations in
> configurations: powerpc-linux-gnu as well as powerpc-eabi are needed
> for almost each individual target.
>
> I reckon that I only need build:
>
> * GDB in both eabi and linux configurations per host; any desired
> target can be debugged by doing a 'set architecture' for it.
>
> That way the number of GDB's built is two per host.
>
> as against:
>
> * A GDB per (host, target) combination of interest.
>
> Which will needless to say, will result in a large number of
> GDB executables needed to be built.
>
> Please could you tell me if my reasoning is correct or am I missing
> something essential?
>
> Thank you very much for your help.
>
> Best Regards,
> Anmol P. Paralkar
>
>
prev parent reply other threads:[~2007-05-18 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 21:43 Anmol P. Paralkar
[not found] ` <655C3D4066B7954481633935A40BB36F041300@ussunex02.svl.access-company.com>
2007-05-18 13:51 ` Anmol P. Paralkar [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=Pine.LNX.4.64.0705180843520.4318@ld0159-tx32.am.freescale.net \
--to=b07584@freescale.com \
--cc=gdb@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