From: Michael Snyder <msnyder@vmware.com>
To: gdb-patches@sourceware.org, Michael Snyder <msnyder@vmware.com>
Subject: Re: Remove m68k-elf special cases from gdb.trace
Date: Mon, 02 Nov 2009 02:53:00 -0000 [thread overview]
Message-ID: <4AEE49A7.8040506@vmware.com> (raw)
In-Reply-To: <20091102012332.GA31878@caradoc.them.org>
Daniel Jacobowitz wrote:
> Our tree has carried around (an older version of) this patch for some
> time.
>
> Once upon a distant past, when tracepoint support was first added, GDB
> supported some sort of EMC device (probably a NAS or similar?) with an
> m68k processor. It was a bit different from other GDB targets and the
> main interest was tracepoints rather than full debugging. So bits
> sprang up in the testsuite to accomodate this device.
>
> They were only conditioned on "m68k-*-elf" (or at least, ended up that
> way). We happen to build toolchains for ColdFire processors which
> also match m68k-*-elf. Running the EMC tracepoint stub on them,
> unsurprisingly, yields poor results.
>
> I could have cleaned this up some other way, but I strongly suspect
> the system we're supporting is no longer deployed - or at least is not
> used with any current version of GDB. Does anyone know otherwise?
> Michael, your name is on some of the original changelog entries for
> these files; CC'd in hopes you know what's become of this target.
It's ok with me, if it's ok with Stan. ;-)
next prev parent reply other threads:[~2009-11-02 2:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 1:24 Daniel Jacobowitz
2009-11-02 2:53 ` Michael Snyder [this message]
2009-11-03 18:39 ` Stan Shebs
2009-11-05 20:09 ` Daniel Jacobowitz
2009-11-10 12:49 ` Pedro Alves
2009-11-10 18:15 ` Stan Shebs
2009-11-10 19:37 ` Pedro Alves
2009-11-10 20:18 ` Eli Zaretskii
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=4AEE49A7.8040506@vmware.com \
--to=msnyder@vmware.com \
--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