From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id D21aNzo0YmAhUwAAWB0awg (envelope-from ) for ; Mon, 29 Mar 2021 16:10:34 -0400 Received: by simark.ca (Postfix, from userid 112) id D492D1E965; Mon, 29 Mar 2021 16:10:34 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=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 471E81E01F for ; Mon, 29 Mar 2021 16:10:34 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id F0C8C3850418; Mon, 29 Mar 2021 20:10:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F0C8C3850418 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1617048634; bh=dcMcellmDSraNsXEfb0/Bz+Rq1seNiYYG5JzMLVMpyY=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=GGMgMigWVVm3/U2/FH10UK/lTWeaHx0/m+1uJuTmA6014wQ5NUiLYEWY5RRsk6vjA 4nVkTreDt/MXAyTKfdc6otMoFR6bxHAVDC6yKcku/ffoa9UDEzKe6eQx8oNVUvgh2l JHHdUXgiMpNXU64csFAVXXdQxdWCVw1Wbt5P3vds= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id EF5673850418 for ; Mon, 29 Mar 2021 20:10:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EF5673850418 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 12TKANVD028712 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Mar 2021 16:10:28 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 12TKANVD028712 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 6BC191E01F; Mon, 29 Mar 2021 16:10:23 -0400 (EDT) Subject: Re: Remote query for structure layout To: Philippe Waroquiers , =?UTF-8?Q?Thomas_Wei=c3=9fschuh?= References: <0e328e95-5035-4de6-9b44-b83ffab38662@t-8ch.de> <51319e86-d463-475c-ad50-b998ac507463@t-8ch.de> <63fba577-8dfd-f04b-2bc4-64645a084328@polymtl.ca> Message-ID: Date: Mon, 29 Mar 2021 16:10:23 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Mon, 29 Mar 2021 20:10:23 +0000 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: Simon Marchi via Gdb Reply-To: Simon Marchi Cc: gdb@sourceware.org Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" On 2021-03-29 4:02 p.m., Philippe Waroquiers wrote: > On Mon, 2021-03-29 at 15:42 -0400, Simon Marchi via Gdb wrote: >> So I would lean towards a home-grown format, but it's more work to >> ensure it is extensible if we want to include more information in the >> replies in the future. > > Wouldn't it be possible to have the target sending back some (maybe limited > and/or partial) 'standard debug info' (such as dwarf) for these types ? > > I have a very limited knowledge of dwarf, so no idea if it is easy > to have 'small scale' debug info being returned by the target > (e.g. by having the needed dwarf entries linked as binary data > inside the target, or generated by the target). > > This might allow to reuse the existing GDB dwarf parser and likely > give a flexible enough description 'language'. It's the other way around. In the problem at hand, GDB has all the information and it's the target who queries GDB for symbol and types. Simon