Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: macro@codesourcery.com (Maciej W. Rozycki)
Cc: brobecker@adacore.com (Joel Brobecker),
	palves@redhat.com (Pedro Alves),
	       gdb-patches@sourceware.org (GDB Patches)
Subject: Re: eliminate deprecated_insert_raw_breakpoint.  what's left.
Date: Thu, 11 Sep 2014 11:50:00 -0000	[thread overview]
Message-ID: <201409111150.s8BBoXiL001461@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1409101840160.27075@tp.orcam.me.uk> from "Maciej W. Rozycki" at Sep 10, 2014 08:11:05 PM

Maciej W. Rozycki wrote:

>  Now that you mention it there is this statement:
> 
>   sym = lookup_symbol (MDEBUG_EFI_SYMBOL_NAME, b, LABEL_DOMAIN, 0, NULL);
> 
> in `mips-mdebug-tdep.c' (in `non_heuristic_proc_desc') indeed, however 
> it's just a fallback in the case where no PDR record has been found.  
> This part can be removed if IRIX support was dropped, we don't expect to 
> have a `.mdebug' section on non-IRIX MIPS ELF targets, so that would 
> become dead code.  The structure of PDR itself is documented in [1] and is 
> only a subset of what a `.mdebug' section would include.

OK, I see.  Looking at gas sources, I can now see that it will create a
.pdr section instead of .mdebug (unless ECOFF debugging is enabled).

> > Also, do you happen to know if on other (non- OSF/1) Alpha platforms the
> > .mdebug debug format is ever used?
> 
>  On Alpha/Linux you'll get it with `-gstabs', although that'll be along 
> some DWARF information for some reason, at least in the somewhat dated 
> version of Alpha GCC I have, e.g.:

Thanks for the info!  Looking through GCC and GAS sources, this is triggered
by GCC passing the -mdebug flag to GAS when it gets -gstabs.  In fact, there
is also a code path on Mips to pass -mdebug to GAS; but this needs the -gcoff
GCC option ...

So in any case, it seems that once IRIX and OSF are gone, we no longer need
to support the ECOFF file format, but there are still ways to generate the
ECOFF *debug* format (even though non-default) on two Linux platforms.  Well,
I guess there's currently no need to remove GDB support for that  ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2014-09-11 11:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.1.10.1409101553070.27075@tp.orcam.me.uk>
2014-09-10 16:45 ` Ulrich Weigand
2014-09-10 19:11   ` Maciej W. Rozycki
2014-09-11 11:50     ` Ulrich Weigand [this message]
2014-09-08 17:46 Pedro Alves
2014-09-08 19:24 ` Joel Brobecker
2014-09-08 21:34   ` Joel Brobecker
2014-09-08 22:50     ` Pedro Alves
2014-09-09  0:25       ` Peter Schauer
2014-09-09  0:16     ` Peter Schauer
2014-09-09 11:39       ` Ulrich Weigand
2014-09-09 12:38         ` Peter Schauer
2014-09-09 21:25           ` Ulrich Weigand
2014-09-10 12:21             ` Joel Brobecker
2014-09-10 13:15               ` Ulrich Weigand
2014-09-10 15:22                 ` Pedro Alves
2014-09-09 21:48   ` Ulrich Weigand
2014-09-10 12:29     ` Joel Brobecker
2014-09-10 14:45       ` Ulrich Weigand
2014-09-10 15:21         ` Pedro Alves
2014-09-10 15:50           ` Maciej W. Rozycki
2014-09-10 15:50           ` Joel Brobecker
2014-09-10 16:00             ` Sergio Durigan Junior
2014-09-10 16:36             ` Ulrich Weigand
2014-10-07  0:25         ` Stan Shebs
2014-09-09 17:33 ` Pedro Alves

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=201409111150.s8BBoXiL001461@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=palves@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