public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arnez at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54887] gdb test case failure with mi-var-rtti
Date: Wed, 24 Oct 2012 17:52:00 -0000	[thread overview]
Message-ID: <bug-54887-4-dg6gldTzPT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54887-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54887

--- Comment #5 from Andreas Arnez <arnez at linux dot vnet.ibm.com> 2012-10-24 17:51:44 UTC ---
(In reply to comment #4)

>  <2><32e>: Abbrev Number: 27 (DW_TAG_lexical_block)
>     <32f>   DW_AT_low_pc      : 0x400758
>     <337>   DW_AT_high_pc     : 0x38 0x0
>  <3><33f>: Abbrev Number: 28 (DW_TAG_variable)
>     <340>   DW_AT_name        : d

Such a whole-subprogram lexical block is still generated by mainline gcc at
r192761.  I verified this on x86_64 with use_rtti_for_ptr_test() in
mi-var-rtti.cc.

Note that the lexical block's range is slightly smaller than the subprogram's:
 <1><30d>: Abbrev Number: 26 (DW_TAG_subprogram)
    <30e>   DW_AT_external    : 1       
    <30e>   DW_AT_name        : (indirect string, offset: 0x35f):
use_rtti_for_ptr_test 
    <312>   DW_AT_decl_file   : 1       
    <313>   DW_AT_decl_line   : 30      
    <314>   DW_AT_linkage_name: (indirect string, offset: 0x173):
_Z21use_rtti_for_ptr_testv    
    <318>   DW_AT_low_pc      : 0x400750        
    <320>   DW_AT_high_pc     : 0x42 0x0        
    <328>   DW_AT_frame_base  : 1 byte block: 9c        (DW_OP_call_frame_cfa)
    <32a>   Unknown AT value: 2116: 1   
    <32a>   DW_AT_sibling     : <0x386> 
 <2><32e>: Abbrev Number: 27 (DW_TAG_lexical_block)
    <32f>   DW_AT_low_pc      : 0x400758        
    <337>   DW_AT_high_pc     : 0x38 0x0        

Is this expected or not?  If needed, I can open a separate Bugzilla for this.


  parent reply	other threads:[~2012-10-24 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 14:39 [Bug debug/54887] New: " arnez at linux dot vnet.ibm.com
2012-10-10 15:48 ` [Bug debug/54887] " dehao at gcc dot gnu.org
2012-10-10 17:15 ` arnez at linux dot vnet.ibm.com
2012-10-10 17:57 ` dehao at gcc dot gnu.org
2012-10-11  8:29 ` arnez at linux dot vnet.ibm.com
2012-10-24 17:52 ` arnez at linux dot vnet.ibm.com [this message]
2012-10-24 17:56 ` dehao at gcc dot gnu.org
2012-10-24 21:25 ` dehao at gcc dot gnu.org

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=bug-54887-4-dg6gldTzPT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).