From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by sourceware.org (Postfix) with ESMTPS id 7AA74387085F for ; Fri, 31 Jul 2020 15:42:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7AA74387085F IronPort-SDR: K+vLKOXFZ7h4ndkkngTlCYpc3Uo26pv+edOhWcJzeOdn4GA2v94n5wlD/WJgxG9KvvTfvNpjpq Z9tsja/orAaA== X-IronPort-AV: E=McAfee;i="6000,8403,9698"; a="236666937" X-IronPort-AV: E=Sophos;i="5.75,418,1589266800"; d="scan'208";a="236666937" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jul 2020 08:42:43 -0700 IronPort-SDR: Tbe0n8h+lCN2hF6W/bSsiob+2rEJk9fP3YOG5EKGoiESi0QNHNKhR1Xyz1pMdWuE3zfhZlkvq6 /U/DU5W+xDpA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,418,1589266800"; d="scan'208";a="304967708" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga002.jf.intel.com with ESMTP; 31 Jul 2020 08:42:42 -0700 Received: from ulvlx001.iul.intel.com (ulvlx001.iul.intel.com [172.28.207.17]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id 06VFgfZx022533; Fri, 31 Jul 2020 16:42:41 +0100 Received: from ulvlx001.iul.intel.com (localhost [127.0.0.1]) by ulvlx001.iul.intel.com with ESMTP id 06VFgfI6015099; Fri, 31 Jul 2020 17:42:41 +0200 Received: (from taktemur@localhost) by ulvlx001.iul.intel.com with LOCAL id 06VFgfvY015095; Fri, 31 Jul 2020 17:42:41 +0200 From: Tankut Baris Aktemur To: gdb-patches@sourceware.org Subject: [PATCH 0/2] Breakpoint conditions at locations with differing contexts Date: Fri, 31 Jul 2020 17:42:27 +0200 Message-Id: X-Mailer: git-send-email 1.7.0.7 X-Spam-Status: No, score=-10.9 required=5.0 tests=AC_FROM_MANY_DOTS, BAYES_00, KAM_DMARC_NONE, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2020 15:42:46 -0000 Hi, This is a short series about conditional breakpoints where the condition may be invalid at some breakpoint locations because of their context. Currently, GDB does not allow defining a condition if it's not valid at all locations. This series aims at bringing more flexibility: the locations at which the condition expression is invalid are disabled automatically. The first patch is the one that implements the new behavior. The second one is an RFC. Depending on the community comments, I'd like to take a direction and complete it. Regards Baris Tankut Baris Aktemur (2): gdb/breakpoint: disable a bp location if condition is invalid at that location gdb/breakpoint: add a '-force' flag to the 'condition' command gdb/ada-lang.c | 2 +- gdb/breakpoint.c | 224 ++++++++++++++---- gdb/breakpoint.h | 12 +- gdb/doc/gdb.texinfo | 6 + gdb/guile/scm-breakpoint.c | 2 +- gdb/python/py-breakpoint.c | 2 +- .../condbreak-multi-context-included.c | 18 ++ .../gdb.base/condbreak-multi-context.c | 51 ++++ .../gdb.base/condbreak-multi-context.exp | 218 +++++++++++++++++ 9 files changed, 478 insertions(+), 57 deletions(-) create mode 100644 gdb/testsuite/gdb.base/condbreak-multi-context-included.c create mode 100644 gdb/testsuite/gdb.base/condbreak-multi-context.c create mode 100644 gdb/testsuite/gdb.base/condbreak-multi-context.exp -- 2.17.1