From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id x2q+OiygXmIUKQAAWB0awg (envelope-from ) for ; Tue, 19 Apr 2022 07:42:36 -0400 Received: by simark.ca (Postfix, from userid 112) id DD1791F377; Tue, 19 Apr 2022 07:42:36 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.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 79EFE1E150 for ; Tue, 19 Apr 2022 07:42:36 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 08B4D3857344 for ; Tue, 19 Apr 2022 11:42:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 08B4D3857344 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1650368556; bh=lF3bif1vL6amDC2XoiD4fPVx+mBbzzdYKRP4BAtmotg=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=gc/TkgJPzJOnAMQfE2a1FiQVmyD2DJxoAGN0RdYnXeeEYs2snjHFVTNsqQI5RvTPV fTxxjLsd7YkM28qxG9VWM2cH7/PRzksLD0KZQmW7jyib+1vupIXu8PBz9yu5vdCOZO Qgjfya9NDtGOd+dTghjxrPyIvOpTwcqU3pWkYaPo= Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) by sourceware.org (Postfix) with ESMTPS id D9CBC3858D3C for ; Tue, 19 Apr 2022 11:42:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D9CBC3858D3C Received: by mail-lf1-x133.google.com with SMTP id o2so28828517lfu.13 for ; Tue, 19 Apr 2022 04:42:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EvBRTzmZT9k1NfyyJEHRdVUYS6KWTWnk2IAE1QAckuo=; b=F8vGNbn0/PD3tnWSnEhbQSwlofXJaMVSaLB0+9nCCU72uqcKM1jZlYTOdF5ifIk4QI niTbR1hgYZ/pDQnV4AhmlyIplzoM7Z7Ji10A6q2Ioc2p1vEHQOHPgjig9oDcBAyK5SgK DIUElyuXeiQ11iRH/CfABM1LFiv2/0sMNZvL6jBQnmy/N3NpGQzHxqUIPVkf4ZL5ghjo lWx7wkC1EaNLvqYUlW8y2sNsAGsZd+RPvAj/jmzlAiHvhJkPNrkimdJ6ecn4dBQxoXL5 wFr5QB5HEtr5qK2/S5+IGKnIM/9Yzw3LMgSnmHFNOmT+qKnWLxJAoPFXUJjJU5ZFdk0C wMhA== X-Gm-Message-State: AOAM5304NDWd32RFsHhn6RgyGJ+QDIQrePZSvMxWptfghi57Tx15j4eL BMzRAW46YIOJK1Nvf9ovTTwW+7f10e+jtorqi08B7gVzTv7eUg== X-Google-Smtp-Source: ABdhPJw41wgQI43jnVuQoCd9qlh6hMLqb0DSzDWD4wltDZIdwPNchJq3vAenb3EhhcbH8dpfDV0oaE5oXaie9+ahhmA= X-Received: by 2002:a05:6512:3d9f:b0:471:8f33:6779 with SMTP id k31-20020a0565123d9f00b004718f336779mr6991372lfv.117.1650368535307; Tue, 19 Apr 2022 04:42:15 -0700 (PDT) MIME-Version: 1.0 References: <20220412090315.1142824-1-simon.farre.cx@gmail.com> In-Reply-To: Date: Tue, 19 Apr 2022 13:42:04 +0200 Message-ID: Subject: Re: [PATCH v2] gdb/Python: Added ThreadExitedEvent To: Pedro Alves Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: , From: Simon Farre via Gdb-patches Reply-To: Simon Farre Cc: Simon Farre via Gdb-patches Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Pedro> Do other thread events have these same attributes? It seems odd to print lwp and tid, but not pid. Pedro> But why not a ptid object instead? InferiorThread has: In the most recent patch I came to the same conclusion. It now returns the same attributes that InferiorThread holds (global_num, num, ptid and name - details was left out of the v3 patch as I could really get the reasoning for keeping it, but I am open for tips & pointers)