From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ydtlBvyVj2C5OAAAWB0awg (envelope-from ) for ; Mon, 03 May 2021 02:19:40 -0400 Received: by simark.ca (Postfix, from userid 112) id 03C281F11C; Mon, 3 May 2021 02:19:40 -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.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_REPLYTO_END_DIGIT,MAILING_LIST_MULTI, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from 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 331121E01F for ; Mon, 3 May 2021 02:19:39 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 601F53948010; Mon, 3 May 2021 06:19:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 601F53948010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1620022778; bh=jq1dsHDvM3YKs3BJ0+L1fjjXQC8De/4D0I2uhShKivo=; 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=pTHmpP8hoQSpdPzEyw+e3c64Az6t77lVYXWZlqJwFHPSNm/PTlGheuZn12quKwKsu LskEzo1sbPw3Qbjl4XEXViQXgr+suv6smuQrJSwmkbbEwraZMi5Lcx5xcOxvKvg8ru 5WU0HrIJGdtiA3VzSy4E3Lwc8gASBWnasB/CMGVA= Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by sourceware.org (Postfix) with ESMTPS id 0CC123947C3D for ; Mon, 3 May 2021 06:19:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0CC123947C3D Received: by mail-lf1-x12b.google.com with SMTP id x19so6490027lfa.2 for ; Sun, 02 May 2021 23:19:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8CVXlA2fPEXXlo0WAzcfc/v9B6hG5emd/27JjKRWyxs=; b=FHAznTL8ErnA2kYBEdo9KQrvnFWmal7H/h3y/fkt1OAAlTibi5BAPCnRBwBD7PnU9c RaerDzEkhG6PgXof9ZvUOuRjnEBPHvy78D6sbM6YbeHUiJozTITvPuFDej9RuT8rsRvp WCy7rbt423hstFpqaqDPPE7pMN1R+lVwo8GV6/dP0Sfyzt36Gp3gxL85HIzYGrakw9UM GPAYMcGvGs3Dg78mJ15AssAXXXPq6IZdj/pW5JrP4M5wRgyZfNetBS/TXClkK3L4QnLc DQQ6wLnl8WI3c9CQcJAvAoMPAbzLauqs3BnORIpbMdYT4ex/a43co7rGZKTHgSFLdOXe vmTQ== X-Gm-Message-State: AOAM531uUxKWGpSm+syDcIpcrYg8qjqjtNjrIvaCI6qYsGmjCM6FUa5L bETC49RMmFk5OXb7yDz41YRzSqxwCH1bZi/7+Wo= X-Google-Smtp-Source: ABdhPJwldWT7h4AVTKesV6vjCYFBskTDb/K2mSZVaQk4sZLpIHkU67Ml6on+kTUnB3G2niI+XY6K+f3bJCWq4xDGSf0= X-Received: by 2002:a05:6512:3d2:: with SMTP id w18mr12022709lfp.573.1620022774809; Sun, 02 May 2021 23:19:34 -0700 (PDT) MIME-Version: 1.0 References: <0b855daa-7659-7270-ffd3-0b86498008f4@polymtl.ca> In-Reply-To: <0b855daa-7659-7270-ffd3-0b86498008f4@polymtl.ca> Date: Mon, 3 May 2021 11:49:23 +0530 Message-ID: Subject: Re: GDB - hardware server To: Simon Marchi Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Mahesh Bodapati via Gdb Reply-To: Mahesh Bodapati Cc: gdb@sourceware.org Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" Thank You. It looks like I didn't frame my problem correctly. server is sending the target descriptions but I have the problem when there is a mismatch between the "expected number of bytes" and "got number of bytes" for instance, gdb has been built for 32 bit abi by default then case 1: if server send 32 bit target description then we didn't see any error case 2 : if server send 64 bit target descriptions then it results an error saying mismatch between "expected number of bytes" and "got number of bytes" and my question is "how can we support 2nd case ? " can we switch the ABI when we receive 64 bit target description from server ? if yes, how can we do that? or do we need to build a different gdb for 64 bit ABI? Note : We can read the ABI from executable but here we are not giving executable file to the gdb. Thanks, Mahesh B On Fri, Apr 30, 2021 at 11:36 PM Simon Marchi wrote: > On 2021-04-29 1:59 a.m., Mahesh Bodapati via Gdb wrote: > > Hi, > > we have 3 different target descriptions for the same target. > > > > gdb has been built for all the 3 configurations but the 1st target > > configuration is the default description. we are able to set > configurations > > from executable files but how to set the target descriptions from the > > contents of the server. > > > > tar remote host:port ,can I set the target description based on the > > contents[like arch,register size..] from the hardware server.I can only > > see the comparison of what gdb is expecting and what gdb is getting from > > the server. is there a way to change the gdb target descriptions from the > > contents of server ? > > I'm not sure I understand the problem correctly, but the server can send > the XML target description to GDB. > > Simon >