From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 2cvQAz93E2D3DAAAWB0awg (envelope-from ) for ; Thu, 28 Jan 2021 21:47:27 -0500 Received: by simark.ca (Postfix, from userid 112) id 00DFB1EF80; Thu, 28 Jan 2021 21:47:26 -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 4BA151E590 for ; Thu, 28 Jan 2021 21:47:26 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id EF558384B823; Fri, 29 Jan 2021 02:47:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF558384B823 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1611888446; bh=USbA3AryoIgWzekvV+1uOZiaJbecIjwcgSXAVCnHYa4=; 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=Ozk9f0eL0WW4ag5VUPUBTALwPiLSlIZPl2cq07G5l4IJdjNrv0M8MwQL40KuXs0ce SQH2QvdDTs6YXSamzHCCW/myC9om+ro0XFp/VcJJf8C7zndLSeITVLqqTE+Ew9fq45 EkAiwv6H9O/vmUKgyItbHosN+ivaNd9XCFuBh06g= Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) by sourceware.org (Postfix) with ESMTPS id D04FC384B823 for ; Fri, 29 Jan 2021 02:47:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D04FC384B823 Received: by mail-io1-xd2d.google.com with SMTP id n2so7816504iom.7 for ; Thu, 28 Jan 2021 18:47:23 -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=USbA3AryoIgWzekvV+1uOZiaJbecIjwcgSXAVCnHYa4=; b=LrBfO2zcTKg0cbD+EHI2dHeLrzgQQgnrz3f/9PJ5VU67xmA1hngFOlDzrYfBDepa5q C7m77Ila9mCyn3pSrixzQjGG4ArWmH9MvccgRp3IY9DwvuKJ7+AxDMJvkXJ8llDrMgA3 4XGkHw+WtDcx4TDfopWN0uVlnqp43tHboFGbDj/9XA02rVzt2b56TTIqYhupdgxoPDCb Z5kBpaFLi1VpUciJD8+0kUTD/l1oY0kLimESY255SGJqftljw1om4eppzPQy/kPY++7N wGOl52/Fav065RbcV36dL+Gdh+nd3Zg/xhA8eFjIr9b2fncPU43rguOg2DDnko8elsFE 37Ow== X-Gm-Message-State: AOAM5332SGp/4xssDM7nzRdas6tbT8LZ8YSsaMoTVzXwdqZvTnOFLw16 htuUTUPUI35LmISiwutLAqv5mPifvSiRAG+2QX5kLFAo2Uo= X-Google-Smtp-Source: ABdhPJwStz/1Gs8Cxje+GVra1S05L1TSy8JUS1Xyp9PvPg4CNcrY1CmkSxXa7TX3iK2hF73G8rTzusoVWey7fUZc1/E= X-Received: by 2002:a05:6602:24cb:: with SMTP id h11mr1825210ioe.79.1611888443205; Thu, 28 Jan 2021 18:47:23 -0800 (PST) MIME-Version: 1.0 References: <83y2gdx9ae.fsf@gnu.org> In-Reply-To: Date: Thu, 28 Jan 2021 18:47:11 -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:33 PM Peng Yu wrote: > > 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. > > So, you get to decide it? The community gets to decide it. Not you. The community responded in the typical way it has for years. If that is unacceptable to you, then you don't seem to be a part of the community. > > How many patches do have in gdb again? > > I don't see this is a relevant question here. If you want to ask that > question, go to gdb-patches. The relevance is that you have not been a part of the community in the past, but you expect it to work in a very particular way, and it has never worked that way. Why should it change now, just for you? Someone who has never contributed in any way to the community? You seem to be confusing Peng's problem with "other people's problem". You came to the mailing list with a problem. That was Peng's problem. We would like to help you with your problem, but whether we can or can't doesn't make it our problem. Someone gives you an answer that doesn't solve your problem? That's your problem, not the answerer's problem. Your problem is not our problem. How we answer doesn't make it our problem.