From: Christian Biesinger via Gdb <gdb@sourceware.org>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: How to display instructions around the current instuction?
Date: Thu, 28 Jan 2021 18:41:54 +0100 [thread overview]
Message-ID: <CAPTJ0XGbWXS69J=RjComBDSPtDNA+2n9Fqv2ASha6puQiiGFnw@mail.gmail.com> (raw)
In-Reply-To: <CABrM6wkwQB3yVPufBGCFO8_q4=parx_kPbq0+3EmP6dQoneiWQ@mail.gmail.com>
On Thu, Jan 28, 2021 at 6:37 PM Peng Yu via Gdb <gdb@sourceware.org> wrote:
>
> I have already thanked other people who send correct answers. But
> helping by definition should making sure the answers are correctly. It
> is not a valid excuse to say to post untested wrong results are OK
> because of "helping".
>
> If an answers is not correct, it should not be sent in the first
> place. In stackoverflow, wrong answers can be deleted. But mailing
> lists don't have this options. Therefore, the senders should make sure
> the correctness of the answers before sending them out.
I hate to take this further offtopic but would like you to consider
that if people were required to test all suggestions first, 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.
Christian
>
> On 1/28/21, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Thu, 28 Jan 2021 11:06:55 -0600
> >> From: Peng Yu via Gdb <gdb@sourceware.org>
> >> Cc: gdb@sourceware.org
> >>
> >> Please test your recommendation before sending it out. It is not
> >> appropriate to waste other people's time.
> >
> > Hey, no one here works for you, you know! So please appreciate that
> > people are "wasting their time" on helping you achieve your goals, and
> > be thankful.
> >
>
>
> --
> Regards,
> Peng
next prev parent reply other threads:[~2021-01-28 17:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 23:12 Peng Yu via Gdb
2021-01-28 8:48 ` Andreas Schwab
2021-01-28 17:08 ` Peng Yu via Gdb
2021-01-28 18:44 ` Andreas Schwab
2021-01-29 17:38 ` Tavis Ormandy via Gdb
2021-01-28 9:19 ` Stefan Puiu via Gdb
2021-01-28 17:06 ` Peng Yu via Gdb
2021-01-28 17:26 ` Eli Zaretskii via Gdb
2021-01-28 17:37 ` Peng Yu via Gdb
2021-01-28 17:41 ` Christian Biesinger via Gdb [this message]
2021-01-29 2:07 ` Peng Yu via Gdb
2021-01-29 2:22 ` Sterling Augustine via Gdb
2021-01-29 2:32 ` Peng Yu via Gdb
2021-01-29 2:47 ` Sterling Augustine via Gdb
2021-01-28 17:57 ` Eli Zaretskii via Gdb
2021-01-28 18:00 ` Stefan Puiu via Gdb
2021-01-29 2:15 ` Peng Yu via Gdb
2021-01-28 13:11 ` Christian Biesinger via Gdb
2021-01-28 16:50 ` Peng Yu via Gdb
2021-01-28 16:53 ` Christian Biesinger via Gdb
2021-01-28 17:16 ` Peng Yu via Gdb
2021-01-28 17:16 ` Christian Biesinger via Gdb
2021-01-28 17:00 ` Sterling Augustine via Gdb
[not found] ` <CAGOmfbFh+6AJZFsDP8nFH1bs6kntC4khO+YmPkn3LUfcLAspZw@mail.gmail.com>
2021-01-28 17:45 ` Peng Yu via Gdb
2021-01-28 18:27 ` Pedro Alves
2021-01-29 1:58 ` Peng Yu via Gdb
2021-01-29 7:18 ` Eli Zaretskii via Gdb
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='CAPTJ0XGbWXS69J=RjComBDSPtDNA+2n9Fqv2ASha6puQiiGFnw@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=cbiesinger@google.com \
--cc=pengyu.ut@gmail.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