Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc@gcc.gnu.org, GDB <gdb@sources.redhat.com>
Subject: Re: gcc 4.0 generates location list without DW_AT_frame_base
Date: Sat, 01 Jan 2005 19:15:00 -0000	[thread overview]
Message-ID: <20050101191459.GA23014@lucon.org> (raw)
In-Reply-To: <20041231220324.GA5987@lucon.org>

On Fri, Dec 31, 2004 at 02:03:24PM -0800, H. J. Lu wrote:
> On Fri, Dec 31, 2004 at 04:57:17PM -0500, Daniel Berlin wrote:
> > >0x000000000055c84d in add_location_or_const_value_attribute
> > >(die=0x2a96205820,
> > >   decl=0x2a961ad000, attr=DW_AT_location)
> > >   at /export/gnu/src/gcc/gcc/gcc/dwarf2out.c:10108
> > >10108         descr = loc_descriptor (NOTE_VAR_LOCATION
> > >(node->var_loc_note),
> > >(gdb) p *loc_list
> > >$4 = {first = 0x0, last = 0x0, decl_id = 14047}
> > >(gdb)
> > 
> > Oh, that's weird.
> > Wonder why we added it then.
> > anyway, just change
> > if (loc_list)
> > to
> > if (loc_list && loc_list->first)
> 
> I am testing it now. Bootstrap has passed the previous failure. It will
> take a while to finish.

The modified patch works with tls_symbolic_operand in i386. However,
I do see

 <2><427491>: Abbrev Number: 39 (DW_TAG_inlined_subroutine)
     DW_AT_sibling     : <427510>
     DW_AT_abstract_origin: <427159>
     DW_AT_low_pc      : 0x8399aea
     DW_AT_high_pc     : 0x8399b3c
 <3><4274a2>: Abbrev Number: 37 (DW_TAG_formal_parameter)
     DW_AT_abstract_origin: <42716b>
 <3><4274a7>: Abbrev Number: 37 (DW_TAG_formal_parameter)
     DW_AT_abstract_origin: <427177>
 <3><4274ac>: Abbrev Number: 44 (DW_TAG_lexical_block)
     DW_AT_low_pc      : 0x8399aea
     DW_AT_high_pc     : 0x8399b3c
 <4><4274b5>: Abbrev Number: 42 (DW_TAG_variable)
     DW_AT_abstract_origin: <427183>
     DW_AT_location    : 2 byte block: 91 54    (DW_OP_fbreg: -44)
[without DW_AT_frame_base]

I assume it is normal.


H.J.


  parent reply	other threads:[~2005-01-01 19:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-22  1:16 Is this a gcc, gdb or readelf bug? H. J. Lu
2004-12-22 11:09 ` Nick Clifton
2004-12-22 18:25   ` H. J. Lu
2004-12-23  3:43     ` Daniel Jacobowitz
2004-12-30 19:24       ` GDB 6.3 assumes that DW_AT_frame_base exists H. J. Lu
2004-12-30 19:36         ` H. J. Lu
2004-12-30 19:56           ` H. J. Lu
2004-12-30 20:07             ` Daniel Jacobowitz
2004-12-30 20:23               ` Gdb generates location list without DW_AT_frame_base H. J. Lu
2004-12-30 20:28                 ` Daniel Jacobowitz
2004-12-30 20:52                   ` Gdb generates DW_OP_fbreg in " H. J. Lu
2004-12-30 20:56                   ` Gdb generates " Daniel Berlin
2004-12-30 21:05                     ` H. J. Lu
2004-12-31  0:35                       ` Daniel Berlin
2004-12-31 19:57                         ` H. J. Lu
2004-12-31 20:09                           ` Daniel Berlin
2004-12-31 20:11                           ` H. J. Lu
2004-12-31 20:16                             ` Daniel Berlin
     [not found]                         ` <20041231163806.GA1335@lucon.org>
     [not found]                           ` <Pine.LNX.4.60.0412311158280.27590@dberlin.org>
     [not found]                             ` <20041231184405.GA2182@lucon.org>
     [not found]                               ` <Pine.LNX.4.60.0412311451060.6844@dberlin.org>
     [not found]                                 ` <Pine.LNX.4.60.0412311509360.6844@dberlin.org>
     [not found]                                   ` <20041231215010.GA5722@lucon.org>
     [not found]                                     ` <20041231215443.GA5853@lucon.org>
     [not found]                                       ` <Pine.LNX.4.60.0412311656360.6844@dberlin.org>
     [not found]                                         ` <20041231220324.GA5987@lucon.org>
2005-01-01 19:15                                           ` H. J. Lu [this message]
2005-01-01 20:09                                             ` gcc 4.0 " Daniel Jacobowitz
2005-01-01 20:50                                             ` Daniel Berlin

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=20050101191459.GA23014@lucon.org \
    --to=hjl@lucon.org \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.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