Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Kai Schuetz <Kai.Schuetz@synopsys.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Crash triggered by DWARF debug info: Any ideas ?
Date: Wed, 13 Feb 2013 17:49:00 -0000	[thread overview]
Message-ID: <874nhgm7dk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <15151570812B8041A31A98C098B7E751042EDC@DE02WEMBX2.internal.synopsys.com>	(Kai Schuetz's message of "Wed, 13 Feb 2013 11:45:11 +0000")

>>>>> "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


      reply	other threads:[~2013-02-13 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 16:38 Kai Schuetz
2013-02-12 19:25 ` Tom Tromey
2013-02-13 11:45   ` Kai Schuetz
2013-02-13 17:49     ` Tom Tromey [this message]

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=874nhgm7dk.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Kai.Schuetz@synopsys.com \
    --cc=gdb@sourceware.org \
    /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