From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67956 invoked by alias); 25 Aug 2018 06:09:35 -0000 Mailing-List: contact gdb-testers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-testers-owner@sourceware.org Received: (qmail 67946 invoked by uid 89); 25 Aug 2018 06:09:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: kwanyin.sergiodj.net Received: from kwanyin.sergiodj.net (HELO kwanyin.sergiodj.net) (158.69.185.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 25 Aug 2018 06:09:33 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [binutils-gdb/gdb-8.2-branch] Record explicit block ranges from dwarf2read.c From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Message-Id: <8cad3755f9d24f236699ecf4100c116095f7ab01@gdb-build> Date: Sat, 25 Aug 2018 10:00:00 -0000 X-SW-Source: 2018-q3/txt/msg04686.txt.bz2 *** TEST RESULTS FOR COMMIT 8cad3755f9d24f236699ecf4100c116095f7ab01 *** Author: Kevin Buettner Branch: gdb-8.2-branch Commit: 8cad3755f9d24f236699ecf4100c116095f7ab01 Record explicit block ranges from dwarf2read.c This change sets BLOCK_RANGES for the block under consideration by calling make_blockranges(). This action is performed in dwarf2_record_block_ranges(). It should be noted that dwarf2_record_block_ranges() already does some recording of the range via a call to record_block_range(). The ranges recorded in that fashion end up in the address map associated with the blockvector for the compilation unit's symtab. Given an address, the addrmap provides a fast way of finding the block containing that address. The address map does not, however, provide a convenient way of determining which address ranges make up a particular block. While reading a set of ranges, a vector of pairs is used to collect the starting and ending addresses for each range in the block. Once all of the ranges for a block have been collected, make_blockranges() is called to fill in BLOCK_RANGES for the block. The ranges are stored for the block in the order that they're read from the debug info. For DWARF, the starting address of the first range of the block will be the entry pc in cases where DW_AT_entry_pc is not present. (Well, that would ideally be the case. At the moment DW_AT_entry_pc is not being handled.) gdb/ChangeLog: * dwarf2read.c (dwarf2_record_block_ranges): Fill in BLOCK_RANGES for block.