From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 696 invoked by alias); 13 Aug 2013 07:41:03 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 679 invoked by uid 89); 13 Aug 2013 07:41:02 -0000 X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,FROM_12LTRDOM,KHOP_RCVD_UNTRUST,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL autolearn=no version=3.3.2 Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 13 Aug 2013 07:41:02 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1V99Dw-000714-9a from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Tue, 13 Aug 2013 00:41:00 -0700 Received: from SVR-ORW-FEM-03.mgc.mentorg.com ([147.34.97.39]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 13 Aug 2013 00:40:59 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-03.mgc.mentorg.com (147.34.97.39) with Microsoft SMTP Server id 14.2.247.3; Tue, 13 Aug 2013 00:40:58 -0700 From: Yao Qi To: Subject: [PATCH 0/2] Test case on entry values Date: Tue, 13 Aug 2013 07:41:00 -0000 Message-ID: <1376379586-24150-1-git-send-email-yao@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-08/txt/msg00327.txt.bz2 Hi, In the review of the patch which adds '--skip-unavailable' to skip unavailable locals and arguments, Pedro pointed that "entry value" should be considered too. The code is not hard, but the test case is harder than the code. We have to make sure that 1) necessary DIEs are generated, 2) set up a case that argument is available but entry value is not. We choose the test to arguments and entry values when GDB is examining trace frames, because something can be unavailable. This situation is not tested in current testsuite, and this test can be reviewed committed independently. Patch 1/2 is to generate dwarf using Dwarf Assembler to test "entry values" are shown correctly. At this point, gdb.trace/entry-values.exp is still a dwarf test, nothing to do with trace. Patch 2/2 is to use tracepoint, to collect data, to test what happen when argument is available and entry value is not. Most of gdb.trace/etnry-values.exp is a dwarf test, and we can move them to gdb.dwarf2 and copy necessary bits in gdb.trace. I didn't do that because it will cause some duplication. *** BLURB HERE *** Yao Qi (2): Test case for entry values. Test entry values in trace frame gdb/testsuite/gdb.trace/entry-values.c | 50 ++++++ gdb/testsuite/gdb.trace/entry-values.exp | 274 ++++++++++++++++++++++++++++++ gdb/testsuite/lib/dwarf.exp | 8 + 3 files changed, 332 insertions(+), 0 deletions(-) create mode 100644 gdb/testsuite/gdb.trace/entry-values.c create mode 100644 gdb/testsuite/gdb.trace/entry-values.exp -- 1.7.7.6