This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PR22034

From: Mark Mitchell <mark at codesourcery dot com>
To: Jan Hubicka <jh at suse dot cz>
Cc: Daniel Berlin <dberlin at dberlin dot org>, gcc-patches at gcc dot gnu dot org, rth at redhat dot com
Date: Thu, 11 Aug 2005 11:46:43 -0700
Subject: Re: PR22034
References: <20050810191012.GA19694@kam.mff.cuni.cz> <42FA8710.7040602@codesourcery.com> <20050811002914.GB29593@kam.mff.cuni.cz> <42FA9D15.4090808@codesourcery.com> <1123721603.7653.72.camel@linux.site> <20050811095617.GC29593@kam.mff.cuni.cz>

Jan Hubicka wrote:

The decl is _ZTVZ19GetAssertStackTracevE9StackDump (vtable for
GetAssertStackTrace()::StackDump) whose context is the class itself.
Why do we emit debug infos for vtables at first place?

I don't know. I can see that debuggers might be able to use them, though.

I seem to get that probably best thing would be to get the context set
to the type but we don't produce dies for types at all, right?

We must do that. Otherwise, where would be put information about the members of classes?

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304

References:
- PR22034
  - From: Jan Hubicka
- Re: PR22034
  - From: Mark Mitchell
- Re: PR22034
  - From: Jan Hubicka
- Re: PR22034
  - From: Mark Mitchell
- Re: PR22034
  - From: Daniel Berlin
- Re: PR22034
  - From: Jan Hubicka

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]