From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alt-proxy28.mail.unifiedlayer.com (alt-proxy28.mail.unifiedlayer.com [74.220.216.123]) by sourceware.org (Postfix) with ESMTPS id 5A0043858C83 for ; Tue, 8 Mar 2022 22:00:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5A0043858C83 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tromey.com Received: from cmgw12.mail.unifiedlayer.com (unknown [10.0.90.127]) by progateway1.mail.pro1.eigbox.com (Postfix) with ESMTP id 951E81003A10D for ; Tue, 8 Mar 2022 22:00:12 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id RhsKnbGWnctgJRhsKnejbE; Tue, 08 Mar 2022 22:00:12 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=Oq2Kdwzt c=1 sm=1 tr=0 ts=6227d1ec a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=9CmXzllqEj8zdNXo:21 a=IkcTkHD0fZMA:10:nop_charset_1 a=o8Y5sQTvuykA:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=AHmt4OI5AAAA:8 a=FsR8HGBq3Dt58Ug-zQcA:9 a=QEXdDO2ut3YA:10:nop_charset_2 a=fVNfgy8k4vUqOr0WNn8q:22 a=WtIh3GgYe9DOuKHWG0yj:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=wxH7fs+NaUFgZVE0WW7UQasrIsvw6juHl11bnDY2pZI=; b=pLXJIYoyRkQhhCTvS7kwzLMF5h CTXNJs6ymJqlGeeqa/G1Mkhdz5KxjDLrnNe9XMI7c8ZAdSLmz5IZe2kcRjEgDcM5tZMlXaclfmGyb 9C7VqNn2+BfQPj1T9GVO6xyOf; Received: from 75-166-141-253.hlrn.qwest.net ([75.166.141.253]:41860 helo=prentzel) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nRhsJ-001u2k-L1; Tue, 08 Mar 2022 15:00:11 -0700 From: Tom Tromey To: Nat! Cc: gdb@sourceware.org Subject: Re: How to add a second "this" (sort of, or maybe do something totally different) References: X-Attribution: Tom Date: Tue, 08 Mar 2022 15:00:10 -0700 In-Reply-To: (Nat!'s message of "Fri, 25 Feb 2022 01:28:35 +0100") Message-ID: <87a6e02jh1.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 75.166.141.253 X-Source-L: No X-Exim-ID: 1nRhsJ-001u2k-L1 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 75-166-141-253.hlrn.qwest.net (prentzel) [75.166.141.253]:41860 X-Source-Auth: tom+tromey.com X-Email-Count: 2 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3023.0 required=5.0 tests=BAYES_00, BODY_8BITS, DKIM_SIGNED, DKIM_VALID, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: , X-List-Received-Date: Tue, 08 Mar 2022 22:00:14 -0000 >>>>> ">" =3D=3D Nat! writes: >> The actual method parameters are accessed indirectly through >> "_param".=C2=A0 So the functions may have looked like this in the >> Objective-C source code: >> int=C2=A0=C2=A0=C2=A0=C2=A0 foo1:(int) a :(void *) b; >> void foo2:(double) a :(void *) b; >> char=C2=A0 *foo3:(int) a :(int) b :(int) c; If this is an Objective-C compiler and/or ABI thing, then gdb could be taught about it directly, I suppose. I'm not sure how well the existing Objective-C code in gdb works, so it may require other changes as well. >> I am looking for the least effort route to support something like this >> for "_param" as well, in gdb. What would be really great, would be to=20 >> also show the struct fields in the stack trace instead of "_param". gdb has limited support for this kind of thing. I don't think there's a good way, currently, do augment 'print' like this. That would requiring hooking into expression parsing / evaluation somehow. For stack traces in particular, a "frame filter" can synthesize 'variables' like this. >> Getting the compiler to output some fake dwarf >> "DW_TAG_formal_parameter" for each struct field with a computed dwarf >> expression, is maybe the proper way it could be done. But that's not >> least effort for me by a long shot. Parameters are tricky because gdb can also do inferior calls, so it has to understand some of these details in a way that DWARF doesn't express. Tom