This is the mail archive of the gdb@sourceware.org mailing list for the GDB 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: Crash triggered by DWARF debug info: Any ideas ?

From: Tom Tromey <tromey at redhat dot com>
To: Kai Schuetz <Kai dot Schuetz at synopsys dot com>
Cc: "gdb\ at sourceware dot org" <gdb at sourceware dot org>
Date: Wed, 13 Feb 2013 10:49:27 -0700
Subject: Re: Crash triggered by DWARF debug info: Any ideas ?
References: <15151570812B8041A31A98C098B7E75104291D@DE02WEMBX2.internal.synopsys.com> <87liatnxmi.fsf@fleche.redhat.com> <15151570812B8041A31A98C098B7E751042EDC@DE02WEMBX2.internal.synopsys.com>

>>>>> "Kai" == Kai Schuetz <Kai.Schuetz@synopsys.com> writes:

Kai> What is the relation of DWARF info and (static?) blocks ?
Kai> I assume there should be one static block per compilation unit ?

Yeah.  There is a comment in block.h that explains it.
Basically each CU has a global block and a static block,
and then various sub-blocks representing scopes in the program.

Kai> With "newer gdb" I assume you refer to one checked out CVS since 7.5.1
Kai> is the latest release ?

Yes, or git.

Tom

References:
- Crash triggered by DWARF debug info: Any ideas ?
  - From: Kai Schuetz
- Re: Crash triggered by DWARF debug info: Any ideas ?
  - From: Tom Tromey
- RE: Crash triggered by DWARF debug info: Any ideas ?
  - From: Kai Schuetz

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