From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id oXQNEju/wGAbAwAAWB0awg (envelope-from ) for ; Wed, 09 Jun 2021 09:16:43 -0400 Received: by simark.ca (Postfix, from userid 112) id 3C3AA1F163; Wed, 9 Jun 2021 09:16:43 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,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 5FBEC1E813 for ; Wed, 9 Jun 2021 09:16:41 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C202A3984007 for ; Wed, 9 Jun 2021 13:16:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C202A3984007 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1623244600; bh=/EhhgRRCgz4M7sMU/2YiiOJ2tXACwvjhUAn4bx5mGqQ=; 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=lMsnrFUXuhkJz4Pm+uXV9QO/4uTdEO8d4BPaj0FPimMNt6zH3Rn23fwQHVPqoAR8e 3gif01EOk8XTHOpEG+0/eCG9SjN2tSbtwH+p1dPpeuso3W6x8cl1FD8xV2CK97QMo3 EYNVaf7RqeH+gAn7HbSL7vVxyiFQeWEEz3p4/+yw= Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) by sourceware.org (Postfix) with ESMTPS id 45981385503A for ; Wed, 9 Jun 2021 13:16:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 45981385503A Received: by mail-ua1-x930.google.com with SMTP id n61so12854096uan.2 for ; Wed, 09 Jun 2021 06:16:19 -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:content-transfer-encoding; bh=/EhhgRRCgz4M7sMU/2YiiOJ2tXACwvjhUAn4bx5mGqQ=; b=VvzdfAJjTIYNofMmhp5sSuh6tIjKUfpLi3qXUKycGDoSsqhGEtWkyBxsotZK4HKD5e pJNSE3plvxamJbPCnS/un4ZJvB7fHDdR1CZncB3zZa+hcxgEv6sCdeD4PH3l9KMX7i+q EViao/9dMuJOWzoPBs+ktxFNptyCpdZfQHydASVcKlKv2vvy7uFUUOFAvVuPW+UrFVj9 PnF6AODUuVbieHRGBJb/MpU/pkRh5r1ZbquKF3uqGfbBdteJXfxTQzTYDW1CWXRa1T42 +rvLWQOTlnXS5dtBpOU9UdOCRWhM4ZL3LZS0kjM6CPw3U4U5X6+CNjl1OUyhqQ4VtGUm V/HA== X-Gm-Message-State: AOAM531sGASgLfymmX3Bcix22jp5gKvPynY9qQqZ1Tfwkm+Mc4GA/N40 g2GLCv1yxUSTCb2y2VZ+hgOw+xmnLPLUjo4/A51BIotAd57JvJGC X-Google-Smtp-Source: ABdhPJyKjsjU7otKI9JoLGI+XfBs3UScfZKL9uY3D2JGiYbpzXvsjlXv2Iii2fC6MfUkAHqYVik3rbANtcvovShVqJw= X-Received: by 2002:ab0:6947:: with SMTP id c7mr16424153uas.116.1623244578892; Wed, 09 Jun 2021 06:16:18 -0700 (PDT) MIME-Version: 1.0 References: <831r9bdxpj.fsf@gnu.org> <83zgvzcho1.fsf@gnu.org> In-Reply-To: <83zgvzcho1.fsf@gnu.org> Date: Wed, 9 Jun 2021 16:16:08 +0300 Message-ID: Subject: Re: [PATCH] TUI disassembly window improvemenmt To: Eli Zaretskii Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: Vasili Burdo via Gdb-patches Reply-To: Vasili Burdo Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Eli, please take look at screenshots I posted: https://imgur.com/a/GlkVXGi They show disassembly starting from the same address. >if some other function is referenced in the disassembly, it will now be in= visible, right? No. Only "address" part for disassembly line is changed. "insn" part which contains references is intact. >IOW, you seem to assume that any function names mentioned in the disassemb= ly are always the name of the current function I didn't make any assumptions of this kind. =D1=81=D1=80, 9 =D0=B8=D1=8E=D0=BD. 2021 =D0=B3. =D0=B2 16:05, Eli Zaretski= i : > > > From: Vasili Burdo > > Date: Wed, 9 Jun 2021 15:56:38 +0300 > > Cc: gdb-patches@sourceware.org > > > > > Shouldn't this be optional behavior? Not everyone disassembles only > > > C++ code. > > This patch does not limit disassembly view in any way. > > - The current function name moved from disassembly line to window head= er > > - Offset from function start still present in disassembly line > > - Function start is marked by function name label. > > But AFAIU only the current function's name is visible; if some other > function is referenced in the disassembly, it will now be invisible, > right? > > IOW, you seem to assume that any function names mentioned in the > disassembly are always the name of the current function, but is that > an assumption that is always correct?