From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36499 invoked by alias); 19 May 2019 13:00:23 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 36481 invoked by uid 89); 19 May 2019 13:00:22 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=BAYES_40,FROM_EXCESS_BASE64,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 spammy=UD:xyz, H*r:Unknown, H*MI:xyz, HX-Languages-Length:329 X-HELO: nessuent.xyz Received: from Unknown (HELO nessuent.xyz) (207.154.253.36) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 19 May 2019 13:00:17 +0000 Received: from localhost (ppp089210102059.access.hol.gr [89.210.102.59]) by nessuent.xyz (Postfix) with ESMTPSA id 12D8820B81 for ; Sun, 19 May 2019 13:00:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nessuent.xyz; s=mail; t=1558270805; bh=leB+yZkCdhGU8cZ7LFs8fSs1OFo18HBgL1NLrUaHOUI=; h=Date:From:To:Cc:Subject:From; b=k3LdGVjmvt1T1wnvUR+9owhzC22eQzhzZ1s8MX6dfnZMPAjfF7SO9+R0/7/63IY+Z A6cOhm7mQK9uq1S2CTLv68PnZIr69jtWpBBt3DzN4yb28CisjDrkEu9Ya6IRM5P7k1 cgzDIk3oA0yhCDHFH3DzcwfbsRQFA0f7E0GFce4sQx3fxHXt8dLqX6yzJdbe3iRY4b 0B4Ym8kr1MS876ZCHqd8OCc+TBOUg2LDPoM+nvZNim+VyPgJUZGBwNj7GBI6QvNd+O ByhzZbph2k6kSKqk0KS1QzmyBDuC52Jq5WzjAYxFHsmgKCI+5dYtQN9OWB2jiqUOHh FFpND6bE9/aJg== Date: Sun, 19 May 2019 19:23:00 -0000 From: =?UTF-8?B?8J+QnQ==?= To: gdb@sourceware.org Cc: Message-ID: Subject: Reloading pretty-printers User-Agent: meli 0.0 MIME-Version: 1.0 X-SW-Source: 2019-05/txt/msg00034.txt.bz2 Hello, I'm writing some pretty-printers for a codebase, and when I modify the python files with gdb running, I can't seem to use the new version. giving `source $GDBINIT` or `source $PRETTYPRINTERDOTPY` gives `pretty-printer already registered` Is there a solution to this other than restarting gdb?