From: JediWisdomKeeper via GNU coreutils Bug Reports <bug-coreutils@gnu.org>
To: 66294@debbugs.gnu.org
Subject: bug#66294: Formal Bug Report in paste.c of Coreutils Version 9.0 by Klee
Date: Sun, 01 Oct 2023 11:29:09 +0000 [thread overview]
Message-ID: <zMmx031no6RBt6NRyIQZL2GhJgDeNumNa2Ds2vbG7LuunljRAX9wAP6TalEFx_Kv00q_8xeSq7W1NLQsKOA_wV0ogGjYe8H8jutmnW34YFg=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
I trust this correspondence finds you in good health and high spirits. I am writing to bring to your attention a significant issue that has come to my notice within the "paste.c" module of Coreutils version 9.0.
The issue appears to impact line no. 208 and 212 of paste.c . I have undertaken a comprehensive investigation and documented my findings in a detailed report. In order to facilitate your review, I have attached a PDF document entitled "Klee_Coreutils_Bug_Report.pdf" to this email. This report encompasses a thorough analysis of the problem, inclusive of pertinent information such as error logs and test cases.
I kindly request that you consider this email as an official bug report. Should you require any additional information, clarification, or assistance in addressing this matter, please do not hesitate to reach out to me.
I appreciate your prompt attention to this issue and eagerly anticipate your response.
Yours sincerely,
JediWisdomKeeper
[-- Attachment #2: Klee_Coreutils_Bug_Report.pdf --]
[-- Type: application/pdf, Size: 218505 bytes --]
next reply other threads:[~2023-10-01 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 11:29 JediWisdomKeeper via GNU coreutils Bug Reports [this message]
2023-10-02 1:15 ` bug#66294: Formal Bug Report in paste.c of Coreutils Version 9.0 by Klee Paul Eggert
[not found] ` <TrvSEF6g66CiFIK8vFTJLtmQSA-nmQ-zEZDNEiRiRQjLAVUrruUE3pey7aV_UkjMNu3KN0kv9fxu91rwqUiOnP6qmwsg269Zm_P90KItxqk=@protonmail.com>
2023-10-16 20:14 ` bug#66294: Fwd: " Paul Eggert
2023-10-16 20:49 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='zMmx031no6RBt6NRyIQZL2GhJgDeNumNa2Ds2vbG7LuunljRAX9wAP6TalEFx_Kv00q_8xeSq7W1NLQsKOA_wV0ogGjYe8H8jutmnW34YFg=@protonmail.com' \
--to=bug-coreutils@gnu.org \
--cc=66294@debbugs.gnu.org \
--cc=JediWisdomKeeper@protonmail.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).