Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: Symbol can't be found unless type 'tab'
Date: Mon, 10 Sep 2012 13:18:00 -0000	[thread overview]
Message-ID: <20120910131828.GA13062@host2.jankratochvil.net> (raw)
In-Reply-To: <504DE251.1020702@codesourcery.com>

On Mon, 10 Sep 2012 14:51:29 +0200, Yao Qi wrote:
>  <1><2c>: Abbrev Number: 3 (DW_TAG_variable)
>     <2d>   DW_AT_name        : i
>     <2f>   DW_AT_type        : <0x23>
>     <33>   DW_AT_location    : 0x0      (location list)

I guess because GDB does not like such complicated location expression for
glboal variables.

read_partial_die (const struct die_reader_specs *reader,
        case DW_AT_location:
          else if (attr_form_is_section_offset (&attr))
              dwarf2_complex_location_expr_complaint ();
+
add_partial_symbol (struct partial_die_info *pdi, struct dwarf2_cu *cu)
    case DW_TAG_variable:
      if (pdi->d.locdesc)
        addr = decode_locdesc (pdi->d.locdesc, cu);


There was a nice cleanup of it in:
	[patch 2/2] Fix decode_locdesc for gcc-4.7.x optimized DWARF
	http://sourceware.org/ml/gdb-patches/2011-07/msg00762.html
but I had to later revert it
	[commit] [patch#2] fetch result of locdesc expressions as integer (not address)
	http://sourceware.org/ml/gdb-patches/2011-10/msg00462.html
due to all the hacks on hacks in GDB needing to be cleaned up first.


Regards,
jan


  reply	other threads:[~2012-09-10 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 12:52 Yao Qi
2012-09-10 13:18 ` Jan Kratochvil [this message]
2012-09-12  7:45   ` Yao Qi
2012-09-12  8:07     ` Jan Kratochvil
2012-09-12 11:34       ` Yao Qi
2012-09-12 12:33         ` Jan Kratochvil
2012-09-12 13:37           ` Yao Qi
2012-09-12 13:45             ` Jan Kratochvil

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=20120910131828.GA13062@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=yao@codesourcery.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