Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [PATCH] remove ECOFF
Date: Mon, 19 Aug 2013 18:51:00 -0000	[thread overview]
Message-ID: <201308191851.r7JIpM3B004049@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1376936369-30712-1-git-send-email-tromey@redhat.com> (message	from Tom Tromey on Mon, 19 Aug 2013 12:19:28 -0600)

> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 19 Aug 2013 12:19:28 -0600
> 
> A while ago I proposed deprecating ECOFF support.
> 
>     http://sourceware.org/ml/gdb/2012-12/msg00052.html
> 
> I've finally implemented this.
> 
> Built (--enable-targets=all) and regested on x86-64 Fedora 18.  Of
> course, there wouldn't be any regressions, since this is removing a
> feature not used or tested.  But still.
> 
> If you grep the sources for mdebug, you will still see a few hits.

The problem is that mdebug isn't really tied to ECOFF.  IIRC, the GNU
tools used to emit some basic mdebug code, and people used to add
assembler directives that would emit mdebug frame info.  That code was
useful for getting proper backtraces through code that didn't have
stabd/dwarf debug information.  Did you verify that GDB is still
useful on an Alpha systems after this removal?


  reply	other threads:[~2013-08-19 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 18:19 Tom Tromey
2013-08-19 18:51 ` Mark Kettenis [this message]
2013-08-19 18:57   ` Tom Tromey
2013-08-19 19:02     ` Tom Tromey
2013-08-19 19:41       ` Joel Brobecker
2013-08-19 21:21 ` Maciej W. Rozycki
2013-08-19 23:22   ` Stan Shebs
2013-08-20 15:12   ` Tom Tromey
2013-08-20 15:20     ` Mark Kettenis
2013-08-20 16:19       ` Maciej W. Rozycki
2013-08-20 15:19   ` Joseph S. Myers

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=201308191851.r7JIpM3B004049@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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