From: Andrew Cagney <ac131313@cygnus.com>
To: gdb@cygnus.com
Subject: Re: breakpoint extension for remote protocol
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <3692A11C.B5024D4A@cygnus.com> (raw)
In-Reply-To: <199901050119.RAA19672.cygnus.gdb@jtc.redbacknetworks.com>
"J.T. Conklin" wrote:
> (IMO having "generic" embedded toolchains is essential. It makes no
> sense to have multiple toolchains for essentially the same processor
> (ie. sparc, sparclite, sparclet, etc.) when one would do.)
Agreed.
I think that the difficulties encountered when trying to support cpu variants
within a single GDB are more of a reflection on the GDB architecture then a
problem with the idea of having the debug smarts on the host (rather than the
target).
As Stan noted:
> Those who study recent snapshots will notice that we are doing some
> internal cleanup that will make it easier to support CPU variants
> without kludging.
>
enjoy,
Andrew
next parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199901050119.RAA19672.cygnus.gdb@jtc.redbacknetworks.com>
1999-04-01 0:00 ` Andrew Cagney [this message]
[not found] <199812041858.KAA25185.cygnus.gdb@jtc.redbacknetworks.com>
1998-12-10 19:27 ` Andrew Cagney
1998-12-10 21:46 ` Stu Grossman
1998-12-11 11:59 ` J.T. Conklin
1998-12-11 14:30 ` J.T. Conklin
1998-12-11 11:24 ` J.T. Conklin
[not found] ` <13936.45476.191551.329690.cygnus.gdb@babylon-5.cygnus.com>
1999-04-01 0:00 ` Andrew Cagney
1999-04-01 0:00 ` J.T. Conklin
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Jim Blandy
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` J.T. Conklin
1998-12-04 10:59 J.T. Conklin
1998-12-23 13:07 ` Greg McGary
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=3692A11C.B5024D4A@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@cygnus.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