Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@ACT-Europe.FR>
To: gcc@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: .n suffixes for function names in stabs debug info (GCC 3.1-based compiler)
Date: Fri, 12 Apr 2002 01:28:00 -0000	[thread overview]
Message-ID: <20020412102802.B16134@act-europe.fr> (raw)
In-Reply-To: <20020411150444.A14251@nevyn.them.org>; from drow@mvista.com on Thu, Apr 11, 2002 at 03:04:44PM -0400

> I believe that GCC is wrong, but you are pointing at the wrong error. 
> See below a bit.

Thank you for this well documented answer.

> According to that, your example:
> > .stabs  "inside.0:f(1,1)=(1,1),inside.0,main",36,0,4,inside.0
> 
> should be:
> > .stabs  "inside.0:f(1,1)=(1,1),inside,main",36,0,4,inside.0

Should this be corrected in GCC? There seems to be an easy fix:
Replace DECL_ASSEMBER_NAME by DECL_NAME in

      /* For a nested function, when that function is compiled,
         mention the containing function name
         as well as (since dbx wants it) our own assembler-name.  */
      if (context != 0)
        fprintf (asmfile, ",%s,%s",
                 IDENTIFIER_POINTER (DECL_ASSEMBLER_NAME (decl)),
                 IDENTIFIER_POINTER (DECL_NAME (context)));

I can submit a patch if this is worth it.

> For your information, Jim Blandy and others are working on greatly
> improving GDB's support for nested scopes right now; this may fall out
> of that, especially for the DWARF-2 case.

Thanks, I will keep an eye on their progress. Note that I like DWARF2
but I am also interested in stabs for some of our platforms like AiX.

-- 
Joel


  reply	other threads:[~2002-04-12  8:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11  9:19 Joel Brobecker
2002-04-11 12:04 ` Daniel Jacobowitz
2002-04-12  1:28   ` Joel Brobecker [this message]
2002-04-12  1:43   ` Joel Brobecker
2002-04-12  7:34     ` Daniel Jacobowitz
2002-04-16  6:06       ` Daniel Berlin

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=20020412102802.B16134@act-europe.fr \
    --to=brobecker@act-europe.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sources.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