Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Geoffrey Keating <geoffk@apple.com>
To: Michael Elizabeth Chastain <mec@shout.net>,
	gcc-patches@gcc.gnu.org, gdb@sources.redhat.com,
	# Daniel Jacobowitz <drow@mvista.com>
Subject: Two possible function stabs patches
Date: Wed, 30 Jul 2003 01:05:00 -0000	[thread overview]
Message-ID: <E57EC088-C229-11D7-B17B-0030657EA24A@apple.com> (raw)

OK, so I have not one, but two patches!

The first one is less interesting.  It uses the language's name for the 
function, unless it's a C++ function, in which case it uses the 
(mangled) assembler name.  It'll give a stab like

         .stabs  "__ZN3bar3fooEv:F(0,1)",36,0,2,__ZN3bar3fooEv
or
         .stabs  "foo:F(0,1)",36,0,2,foo.11

The second one uses the 'printable name' for the function.  That is, 
for C it's just the name, and for C++ it's the demangled version of its 
name.  I am not at all sure it'll work, because it gives stabs like:

         .stabs  "int bar::foo():F(0,1)",36,0,2,__ZN3bar3fooEv

which I suspect can't be parsed.

Could someone help me test these?  It needs a machine that can use 
stabs and on which the GDB testsuite doesn't give too many false 
positives.

-- 
Geoff Keating <geoffk@apple.com>


             reply	other threads:[~2003-07-30  1:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  1:05 Geoffrey Keating [this message]
2003-07-30  5:47 Fwd: " Michael Elizabeth Chastain
2003-07-30 21:43 ` Geoffrey Keating
2003-07-30 14:18 Fwd: " Andrew Cagney
2003-08-01 22:36 ` Geoffrey Keating
2003-07-30 22:29 Michael Elizabeth Chastain

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=E57EC088-C229-11D7-B17B-0030657EA24A@apple.com \
    --to=geoffk@apple.com \
    --cc=drow@mvista.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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