From: Peng Yu <pengyu.ut@gmail.com>
To: Sterling Augustine <saugustine@google.com>
Cc: Christian Biesinger <cbiesinger@google.com>,
Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: How to display instructions around the current instuction?
Date: Thu, 28 Jan 2021 20:32:49 -0600 [thread overview]
Message-ID: <CABrM6wkyHcYJe2kJv3PXjO5ZPjz+1WvvPPOq9dNQDr3Fxm89jg@mail.gmail.com> (raw)
In-Reply-To: <CAEG7qUxixL1JT6u1z8sPeYLTAp3HEguEGrruAWJMSwNSD1dTsQ@mail.gmail.com>
On Thu, Jan 28, 2021 at 8:22 PM Sterling Augustine
<saugustine@google.com> wrote:
>
> On Thu, Jan 28, 2021 at 6:07 PM Peng Yu via Gdb <gdb@sourceware.org> 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.
So, you get to decide it?
> 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?
I don't see this is a relevant question here. If you want to ask that
question, go to gdb-patches.
gdb (archives) A list for general discussion about GDB. Any
GDB-related subject not covered by another list is appropriate here;
in practice, most of the discussions are about ideas for future
changes. Patches should be sent to the gdb-patches mailing-list (see
below). Bugs should be reported using the Bug Database.
gdb-patches (archives) For patch submissions and discussion. All patch
submissions and submission discussion should go through this list.
--
Regards,
Peng
next prev parent reply other threads:[~2021-01-29 2:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 23:12 Peng Yu
2021-01-28 8:48 ` Andreas Schwab
2021-01-28 17:08 ` Peng Yu
2021-01-28 18:44 ` Andreas Schwab
2021-01-29 17:38 ` Tavis Ormandy
2021-01-28 9:19 ` Stefan Puiu
2021-01-28 17:06 ` Peng Yu
2021-01-28 17:26 ` Eli Zaretskii
2021-01-28 17:37 ` Peng Yu
2021-01-28 17:41 ` Christian Biesinger
2021-01-29 2:07 ` Peng Yu
2021-01-29 2:22 ` Sterling Augustine
2021-01-29 2:32 ` Peng Yu [this message]
2021-01-29 2:47 ` Sterling Augustine
2021-01-28 17:57 ` Eli Zaretskii
2021-01-28 18:00 ` Stefan Puiu
2021-01-29 2:15 ` Peng Yu
2021-01-28 13:11 ` Christian Biesinger
2021-01-28 16:50 ` Peng Yu
2021-01-28 16:53 ` Christian Biesinger
2021-01-28 17:16 ` Peng Yu
2021-01-28 17:16 ` Christian Biesinger
2021-01-28 17:00 ` Sterling Augustine
[not found] ` <CAGOmfbFh+6AJZFsDP8nFH1bs6kntC4khO+YmPkn3LUfcLAspZw@mail.gmail.com>
2021-01-28 17:45 ` Peng Yu
2021-01-28 18:27 ` Pedro Alves
2021-01-29 1:58 ` Peng Yu
2021-01-29 7:18 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABrM6wkyHcYJe2kJv3PXjO5ZPjz+1WvvPPOq9dNQDr3Fxm89jg@mail.gmail.com \
--to=pengyu.ut@gmail.com \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=saugustine@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).