From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id CLZ1O1+DomRicBQAWB0awg (envelope-from ) for ; Mon, 03 Jul 2023 04:14:23 -0400 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=RRCwIC8u; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id E75821E0BB; Mon, 3 Jul 2023 04:14:23 -0400 (EDT) Received: from server2.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 D77921E00F for ; Mon, 3 Jul 2023 04:14:21 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 4C00E3858281 for ; Mon, 3 Jul 2023 08:14:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4C00E3858281 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1688372061; bh=72z3eWaSkOg7KWsR0rs41FhlOl6DHTiMWJXnqObJlzE=; h=To:Cc:Subject:References:Date:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=RRCwIC8uisqqPFj+TWoNc91X9oTHB2+l/A2bN1gMmyNF4jIOTWo7pLu1wyqUISFUp iJqc9J9Nu3EPxPWf7iuHERUqT3XyM4IsoMb/1NEUja0t1vCcfBvl2uRw2CaBgAkqX8 GJdsQqizm5H9p5EjnYriO+WBumZu4DmyTZ3fzxzg= 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 4723D3858D28 for ; Mon, 3 Jul 2023 08:13:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 4723D3858D28 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-635-Q171E_iyN4qwIzuIYODp4w-1; Mon, 03 Jul 2023 04:13:44 -0400 X-MC-Unique: Q171E_iyN4qwIzuIYODp4w-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 1ACCA803FDF; Mon, 3 Jul 2023 08:13:44 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.9]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5E8F7C00049; Mon, 3 Jul 2023 08:13:43 +0000 (UTC) To: "Aktemur, Tankut Baris via Gdb" Cc: "Aktemur, Tankut Baris" Subject: Re: Using GDB as a Python interpreter References: <87sfa8vwqx.fsf@oldenburg.str.redhat.com> Date: Mon, 03 Jul 2023 10:13:42 +0200 In-Reply-To: (Tankut Baris via Gdb Aktemur's message of "Mon, 3 Jul 2023 07:11:47 +0000") Message-ID: <87jzvh2z0p.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-4.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@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: Florian Weimer via Gdb Reply-To: Florian Weimer Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" * Tankut Baris via Gdb Aktemur: > On Saturday, July 1, 2023 10:53 AM, Florian Weimer wrote: >> I want to run a Python script with GDB, from the shell command line, >> without having to create two files. >>=20 >> I came up with the hack included below, but it's not particularly nice. >> The downside is that the script file name must end in =E2=80=9C.py=E2=80= =9D, which would >> not allow to install the script in /usr/bin for most distributions. I >> don't see a way to override that. > > Based on this comment, I assume you have write access to /usr. > Would you then consider wrapping your script in a Python function > and then installing it in GDB's data directory > (e.g. /usr/share/gdb/python/gdb/function/)? The file would be loaded > automatically by GDB at startup. You can then invoke the Python function > with a single-line GDB command. I was aiming for a one-file solution (and something that could be installed as-is into /usr/bin eventually). Two-file solutions are sort of easy. 8-) Thanks, Florian