Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Stan Shebs <stan@codesourcery.com>,
	  Michael Snyder <msnyder@vmware.com>
Subject: Re: Remove m68k-elf special cases from gdb.trace
Date: Tue, 10 Nov 2009 18:15:00 -0000	[thread overview]
Message-ID: <4AF9ADBE.4060409@codesourcery.com> (raw)
In-Reply-To: <200911101249.03859.pedro@codesourcery.com>

Pedro Alves wrote:
> On Tuesday 03 November 2009 18:39:42, Stan Shebs wrote:
>   
>> 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.
>>>       
>> WP has some background at http://en.wikipedia.org/wiki/EMC_Symmetrix .
>>
>> Ironically, the original tracepoint project was motivated by EMC's
>> PowerPC transition - the 68k bits were just for testing in the meantime.
>> (IIRC EMC never used GDB for 68k-target debugging at all!) So there's
>> nothing lost by ditching those bits, and it will clear the field for
>> updating to modern setup.
>>     
>
> gdb/agentexpr.texi has section "Tracing on Symmetrix" that I
> think should be dropped as well.
>   
Agreed. It's an interesting historical tidbit, but historians can go dig 
up an old rev if they really want to research it.

Stan


  reply	other threads:[~2009-11-10 18:15 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
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 [this message]
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=4AF9ADBE.4060409@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.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