From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id whOxEFtxE2D4CwAAWB0awg (envelope-from ) for ; Thu, 28 Jan 2021 21:22:19 -0500 Received: by simark.ca (Postfix, from userid 112) id 377871EF80; Thu, 28 Jan 2021 21:22:19 -0500 (EST) 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 7CD0E1E945 for ; Thu, 28 Jan 2021 21:22:18 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id E8A59386F019; Fri, 29 Jan 2021 02:22:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E8A59386F019 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1611886938; bh=ocJQy0+HMacCWn6qfRrmc0pJSrHIDYdjpgrUNDsK+bM=; 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=iuTJeTWAhWKpJgHItQCnBB4GgffFsS5D7iUi4z8hUFTQMVXV/TRNsUP/PfI9hiz+A haOwfOp+stCxYc9wdIv9YncK1jHdOdqUbWUMwm4Sfdv7YfLcmvQVdsOkNJO2a/yBQn ls4bKs5cPgsXPQfQpSbD9gnFVyXmdA8hmGDGorhw= Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) by sourceware.org (Postfix) with ESMTPS id 3F8D23857C66 for ; Fri, 29 Jan 2021 02:22:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3F8D23857C66 Received: by mail-io1-xd29.google.com with SMTP id 16so7786741ioz.5 for ; Thu, 28 Jan 2021 18:22:15 -0800 (PST) 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=ocJQy0+HMacCWn6qfRrmc0pJSrHIDYdjpgrUNDsK+bM=; b=aE+sCcLgvLeqwsfqSf+/vueAL/wIjkalS7TgsOyDiPTHIDQKVT3oqzP79hm12yIrDE LArZAYZDgZD2JfjC++rDxD5Jwl74uiJePP37/oDtGgSpsV9L7ZEd06JebFhCWlRG73ic kjjasHyWD8Kh8vZpZBMBfJoj4FHii5MkdEOL1neyDLwvla8XIOXbcd5x2Xd3fm6ZxcVt dNyI+6OS3Kn7cT7mMSscm22CNZpjDB7Yps4PvV1JU7mN64T/v+0zmQGAzbCziDOh4UhF jlZPueWBxI+rNDU0lyIz9I881vw3N1bRwhmeEbS65rpEM8q4s8wFh58CLWsDwGM9Ptgb /0mw== X-Gm-Message-State: AOAM5310NdfcKBwUgks/9tC7u3nd4+UcRK6bJ7SxSFRTOOlWMULnTqw1 qGoXxGc3WRZlyjmtfHHDHvQUMy8aESyXr38rmyi+bA== X-Google-Smtp-Source: ABdhPJw0QDwtdA+VKtEhEXunkVwu56JW5U10aklAEiKO+iBgyPc8XdqDFyYpTPox0+XpyMd8vRhuYwfRBIDpzdWEtjs= X-Received: by 2002:a05:6602:144:: with SMTP id v4mr2240656iot.168.1611886934543; Thu, 28 Jan 2021 18:22:14 -0800 (PST) MIME-Version: 1.0 References: <83y2gdx9ae.fsf@gnu.org> In-Reply-To: Date: Thu, 28 Jan 2021 18:22:03 -0800 Message-ID: Subject: Re: How to display instructions around the current instuction? To: Peng Yu Content-Type: text/plain; charset="UTF-8" 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: Sterling Augustine via Gdb Reply-To: Sterling Augustine Cc: Reuben Thomas via Gdb Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" On Thu, Jan 28, 2021 at 6:07 PM Peng Yu via Gdb wrote: > > > I hate to take this further offtopic but would like you to consider > > that if people were required to test all suggestions first, > > That is not what I meant. See below. > > > many > > responses would not be sent in the first place. For example, I did not > > test my hook-stop suggestion. I am not sure that people would be > > better off in such a world. > > The point is the answer is better to be correct. Remind me: How many contributions have you made to gdb? > If it is known to be > correct, of course, there is no need to test it. But if the sender is > not sure, it is better to test it to make sure. If a sender sends out > a wrong answer, s/he does show respect to the recipient. You have a strange, rather binary view, of "correct" vs "incorrect". Every single idea here does something approximately like what you want. Many people in the past asking similar questions would have been perfectly fine with a wide variety of answers. You might not like it, but you don't get to decide what the proper etiquette in this mailing list. If you decide they aren't exact enough, then, well, not much we can do. But most people who come begging for help from people who are just trying to be kind are willing to at least work with the possible answers, and see if they can adapt them, rather than playing like they are proctoring a test. It is not our job to give you technical support--nor is it this mailing list's reason for existence. You are lucky people are answering at all. I would rather people try to help than refrain from answering in case it isn't exactly what the beggar wanted. That is how this list has always worked in the two-decades I've been a part of it. In fact, you have really no room to insist people help you in any particular way. We have all worked on gdb for years--maybe decades. We have all been active on this list for as long. So insisting we follow your preferences rather than ours is incredibly rude. How many patches do have in gdb again?