From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 0ODDOVOa5GNH7S0AWB0awg (envelope-from ) for ; Thu, 09 Feb 2023 02:01:39 -0500 Received: by simark.ca (Postfix, from userid 112) id DF3D91E15D; Thu, 9 Feb 2023 02:01:39 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=c9lYp3Ch; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 634D61E0D3 for ; Thu, 9 Feb 2023 02:01:39 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C7D38385828E for ; Thu, 9 Feb 2023 07:01:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C7D38385828E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675926096; bh=/xrZRXnoqGNYoUqwDLzyM+5vFTmV7O+UWm+BtQrf6hw=; h=References:In-Reply-To:Date:Subject:To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=c9lYp3ChB6o/bLF7wIttGfS3A1lLWIkfp2dMmGWmcPEoPd3oQDfo2ZhrhfD9ZURUp tVc2WnDTwJAGf/0FOdYE/C86e5K56ni3SyU6Cm6MQTJhTPSg3voST3OxyCHZgIQgLK qCqmlQ3kPs7oMVEyk6CFuVF3aOSZjcDecYeD/llw= Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by sourceware.org (Postfix) with ESMTPS id 0EC123858C50 for ; Thu, 9 Feb 2023 07:01:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0EC123858C50 Received: by mail-ej1-x62f.google.com with SMTP id ml19so3691359ejb.0 for ; Wed, 08 Feb 2023 23:01:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/amr3roN06jLHxEJwQ3/U9lj+mGTaUW24JsH4/CdvNE=; b=Lip9GZQNMYNSQ2uYbKbdORN0ALlyctPKWq0iwxYki3YIQJMz31s9XhrqlUFd/Op2U9 lsN7PCrmMSqhImSV+kd06xVQciK/sQKwTFjHvgk9UuZ+1Q2nAgozc5HhKLm5Xx1IN/3O 3SfQmubwtNDpMShccPvMl/eTiVY76VFmtNdj0EI8jNuEzlUOsdPOfOsPAfwhBWEEExEg IjjeFRf/4c+TFFmf7GKkx5Ho4ro52eY7YvwY1f9kqwsCnQ0ZgbU4Cp/rZGbmBuKNPd2A VftytZraSVEsL77JVXXXx7jeuAIs9kMIaL37YYL7ENNDwf6Hjm8JROTts/qQ/6g7iE3s mnnQ== X-Gm-Message-State: AO0yUKV98b5UvhywqtFr1kawE9Yyy5RZEPlMAyreWwVRJ4eGlMtIUjb3 dNpkAeeNQBBIzTxgzT9fi1gXNdfkA0BA+enDa+Nsm3vA X-Google-Smtp-Source: AK7set/0IEmOAu8SM7ZwzkgJe4lqz80A49/NfBWP/13eee74L3+kOA0dxlvcmZWTiyQtTQqTqVbWYxcPrGzuZwlJ1iE= X-Received: by 2002:a17:906:5384:b0:86f:5375:9f64 with SMTP id g4-20020a170906538400b0086f53759f64mr2025359ejo.135.1675926060670; Wed, 08 Feb 2023 23:01:00 -0800 (PST) MIME-Version: 1.0 References: <36c20830-7713-bff5-ca88-ea8bc2aab8b5@gnu.org> In-Reply-To: <36c20830-7713-bff5-ca88-ea8bc2aab8b5@gnu.org> Date: Thu, 9 Feb 2023 20:00:49 +1300 Message-ID: Subject: Re: Is there an option to "silent-step"/ "silent-next" (possibly in python and/or mi)? To: Simon Sobisch Cc: GDB Mailing list Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Chris Packham via Gdb Reply-To: Chris Packham Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" On Thu, 9 Feb 2023, 2:44 AM Simon Sobisch via Gdb, wrote: > For "stepping in the current source" (given a mixed-source) I look for a > way to "silent step" / "silent next". > This will be useful for example if you debug within Bison and/or Flex > generated sources and don't want to step through the state / token > machine, having only the Bison / Flex _source_ be visible. > > Getting the source name from the frame and comparing this after a > step/next is no big problem in GDB using python > gdb.selected_frame().find_sal().symtab.fullname() > > Using GDB in TUI mode I commonly "stay" in the source I'm interested in > this way, but the GDB command line gets "flooded" with all the > intermediate frame positions I'm not interested in. > > So: is there a way to do a "step"/"next" with suppressing the normal > output and mi stop events normally send? > > Thank you for any pointers, > Simon > Does the `skip` command do what you want? I use it for skipping uninteresting things like memset() or printf() when stepping. >