From: David Carlton <carlton@kealia.com>
To: gdb <gdb@sources.redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>
Subject: constructors and DW_AT_MIPS_linkage_name
Date: Fri, 13 Feb 2004 17:59:00 -0000 [thread overview]
Message-ID: <m3smheoo71.fsf@coconut.kealia.com> (raw)
I was just looking at the .debug_info for the example given in PR
1553, and I was surprised to see the following (some bits have been
deleted)
.uleb128 0x2 # (DIE (0x25) DW_TAG_structure_type)
.long 0x7b # DW_AT_sibling
.ascii "A\0" # DW_AT_name
.byte 0x1 # DW_AT_byte_size
.uleb128 0x4 # (DIE (0x37) DW_TAG_subprogram)
.long 0x57 # DW_AT_sibling
.byte 0x1 # DW_AT_external
.long .LC0 # DW_AT_name: "operator="
.long .LC1 # DW_AT_MIPS_linkage_name: "_ZN1AaSERKS_"
.long 0x7b # DW_AT_type
.byte 0x1 # DW_AT_artificial
.byte 0x1 # DW_AT_declaration
.byte 0x0 # end of children of DIE 0x37
.uleb128 0x7 # (DIE (0x57) DW_TAG_subprogram)
.long 0x6d # DW_AT_sibling
.byte 0x1 # DW_AT_external
.ascii "A\0" # DW_AT_name
.byte 0x1 # DW_AT_artificial
.byte 0x1 # DW_AT_declaration
.byte 0x0 # end of children of DIE 0x57
.uleb128 0x8 # (DIE (0x6d) DW_TAG_subprogram)
.byte 0x1 # DW_AT_external
.ascii "A\0" # DW_AT_name
.byte 0x1 # DW_AT_artificial
.byte 0x1 # DW_AT_declaration
.byte 0x0 # end of children of DIE 0x6d
.byte 0x0 # end of children of DIE 0x25
The weird thing is that operator= gets a linkage name, but the
constructors don't. I don't think we're prepared to deal with this;
it would explain some weirdnesses that I've seen elsewhere, where
trying to look up a class returns that class's constructor instead.
Is this a known GCC issue? (The above is with GCC 3.2; for GCC
mainline, the debug info for A isn't there at all, but that's a
separate issue.) If so, in what circumstances does it occur?
David Carlton
carlton@kealia.com
next reply other threads:[~2004-02-13 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 17:59 David Carlton [this message]
2004-02-15 1:14 ` Daniel Jacobowitz
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=m3smheoo71.fsf@coconut.kealia.com \
--to=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb@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