This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/8218] ptype claims destructors have arg
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 22 Jan 2013 18:05:34 +0000
- Subject: [Bug c++/8218] ptype claims destructors have arg
- Auto-submitted: auto-generated
- References: <bug-8218-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=8218
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #3 from Tom Tromey <tromey at redhat dot com> 2013-01-22 18:05:34 UTC ---
(In reply to comment #2)
> 0x00000063: DW_TAG_formal_parameter [4]
> 0x00000064: DW_AT_type [DW_FORM_ref4] (cu + 0x0071 => {0x00000071})
> 0x00000068: DW_AT_artificial [DW_FORM_flag] (0x01)
> Shall we close this & open a GCC bug instead? (& change the kfail to an xfail
> referencing the GCC bug - and add the correct pattern so Clang can pass this
> test)
Arguably it is still a gdb bug since the parameter is marked artificial.
I think that gdb may be making an explicit choice here, though, since
c_type_print_args explicitly prints artificial arguments.
There is a GCC bug in this area:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37237
It may not seem related but if you read the comments, the gist
is that GCC is just emitting DWARF for one of the constructors,
whereas it should probably emit DWARF for all of them.
Adding a pattern for clang to pass seems fine to me.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.