Message ID | 20230713102411.2279542-1-blarsen@redhat.com |
---|---|
Headers |
Return-Path: <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 2D38B385735A for <patchwork@sourceware.org>; Thu, 13 Jul 2023 10:24:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2D38B385735A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1689243887; bh=dKyC7Xao/Efi0zPBeb7xsl27U5Yvlk1MW2agkqu2cWE=; h=To:Cc:Subject:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=Nl4sBCdXNJPtulWHVq7qZ+SZLuZ6T9tvZl4Qu9cjyPiYe/dajSIHCXrHE8DnmIoNq 1qkIgGICK67K4NWCP//yYDk8ditg32Hk+c9MagsALY2M85m10Zga+AmIeCfRmcyoaI yYowLb3Xily1zSMFY3xOqdOTvDiqtfxZE7WLJVQw= X-Original-To: gdb-patches@sourceware.org Delivered-To: gdb-patches@sourceware.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 70DB23857736 for <gdb-patches@sourceware.org>; Thu, 13 Jul 2023 10:24:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 70DB23857736 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-119-UVy_NaYlMRSiPZEhAEnCMg-1; Thu, 13 Jul 2023 06:24:21 -0400 X-MC-Unique: UVy_NaYlMRSiPZEhAEnCMg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 87D8A85A58A for <gdb-patches@sourceware.org>; Thu, 13 Jul 2023 10:24:21 +0000 (UTC) Received: from fedora.redhat.com (unknown [10.45.226.146]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 117E340C2063; Thu, 13 Jul 2023 10:24:20 +0000 (UTC) To: gdb-patches@sourceware.org Cc: Bruno Larsen <blarsen@redhat.com> Subject: [PATCH v4 0/4] Small changes to "list" command Date: Thu, 13 Jul 2023 12:24:07 +0200 Message-ID: <20230713102411.2279542-1-blarsen@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/gdb-patches/> List-Post: <mailto:gdb-patches@sourceware.org> List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=subscribe> From: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> Reply-To: Bruno Larsen <blarsen@redhat.com> Errors-To: gdb-patches-bounces+patchwork=sourceware.org@sourceware.org Sender: "Gdb-patches" <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org> |
Series | Small changes to "list" command | |
Message
Guinevere Larsen
July 13, 2023, 10:24 a.m. UTC
I decided to tackle PR cli/30497, and while doing so, Andrew mentioned that it would also be nice if we could explicitly ask GDB to print the current location, so I also decided to add that into a series. The first patch is just some groundwork preparation to make the rest smooth. On the second pass, I realized that 'list +' isn't properly documented, so I added it to the docs as well. After last round of reviews, I changed my approach to fixing cli/30497 to only have a more obvious error message to the end user instead of jumping back to the current location. Changes from v3: * Reordered patches - now '.' comes first so the UX change can reference it * completely rewrote approach to patch 3 * made "list ." no longer throw an error when inferior isn't started Changes from v2: * Addressed Eli's comments * Added Eli reviews. Changes from v1: * added new arguments to the docs * Added patch 4, completely new. * Fixed wording, per Eli's suggestions. Bruno Larsen (4): gdb/cli: Factor out code to list lines around a given line gdb/cli: add '.' as an argument for 'list' command gdb/cli: Improve UX when using list with no args gdb/doc: document '+' argument for 'list' command gdb/NEWS | 9 ++++ gdb/cli/cli-cmds.c | 85 +++++++++++++++++++++++++-------- gdb/doc/gdb.texinfo | 12 ++++- gdb/source.c | 16 +++++++ gdb/source.h | 7 +++ gdb/testsuite/gdb.base/list.exp | 47 ++++++++++++++++-- gdb/testsuite/gdb.base/list1.c | 2 +- 7 files changed, 153 insertions(+), 25 deletions(-)
Comments
>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
Bruno> I decided to tackle PR cli/30497, and while doing so, Andrew mentioned
Bruno> that it would also be nice if we could explicitly ask GDB to print the
Bruno> current location, so I also decided to add that into a series. The first
Bruno> patch is just some groundwork preparation to make the rest smooth. On
Bruno> the second pass, I realized that 'list +' isn't properly documented, so
Bruno> I added it to the docs as well.
Bruno> After last round of reviews, I changed my approach to fixing cli/30497
Bruno> to only have a more obvious error message to the end user instead of
Bruno> jumping back to the current location.
This all looks good to me, modulo a nit I sent earlier.
Thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom