public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: jrs@world.std.com
Cc: gas2@cygnus.com
Subject: Re: ELF line numbers
Date: Tue, 11 Jul 1995 09:33:00 -0000	[thread overview]
Message-ID: <199507111633.MAA21372@sanguine.cygnus.com> (raw)
In-Reply-To: <951322.023610.jrs@world.std.com>

   From: jrs@world.std.com (Rick Sladkey)
   Date: Thu, 22 Jun 1995 02:36:10 EDT

   When I first tried GNU ld on SunOS 4.1.x, I liked the inclusion of
   file, function and line number in undefined error messages.  I finally
   got tired of seeing `.text+0xXXXX' messages and so I tried to add this
   feature for ELF on Solaris 2.x and Linux.  I implemented a simple
   version which will work even without debugging but omits the line
   number (based on the one in aoutx.h).

Thanks.  I checked this in.

   Then as I was about to embark on the full debug version, I realized
   that using the .stabs section will work for Solaris and Linux but not
   DWARF.  In which file should one implement the stabs version?  It
   seems that elfcode.h is too general and elf32-{i386,sparc}.c are too
   specific.

Actually, the GNU tools support .stabs debugging for any ELF target.
That is actually the only to implement C++ debugging in ELF right now,
because g++ does not support DWARF.  So, elfcode.h (actually, the
function is now in elf.c) is the right place to handle both stabs and
DWARF debugging information.

Ian


      reply	other threads:[~1995-07-11  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-06-21 22:40 Rick Sladkey
1995-07-11  9:33 ` Ian Lance Taylor [this message]

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=199507111633.MAA21372@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=jrs@world.std.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).