From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Cc: Julian Seward <jseward@acm.org>
Subject: Re: [PATCH] Replace project contact email with bzip2-devel@sourceware.org.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <38c77651b5696da99560f36d5285741ca9d1b514.camel@klomp.org> (raw)
In-Reply-To: <1562868211-28019-1-git-send-email-mark@klomp.org>
On Thu, 2019-07-11 at 20:03 +0200, Mark Wielaard wrote:
> @@ -829,7 +829,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n )
> " The user's manual, Section 4.3, has more info on (1) and (2).\n"
> " \n"
> " If you suspect this is a bug in bzip2, or are unsure about (1)\n"
> - " or (2), feel free to report it to me at: jseward@acm.org.\n"
> + " or (2), feel free to report it to: bzip2-devel@sourceware.org.\n"
> " Section 4.3 of the user's manual describes the info a useful\n"
> " bug report should have. If the manual is available on your\n"
> " system, please try and read it before mailing me. If you don't\n"
> @@ -852,7 +852,7 @@ void mySIGSEGVorSIGBUScatcher ( IntNative n )
> " The user's manual, Section 4.3, has more info on (2) and (3).\n"
> " \n"
> " If you suspect this is a bug in bzip2, or are unsure about (2)\n"
> - " or (3), feel free to report it to me at: jseward@acm.org.\n"
> + " or (3), feel free to report it to: bzip2-devel@sourceware.org.\n"
> " Section 4.3 of the user's manual describes the info a useful\n"
> " bug report should have. If the manual is available on your\n"
> " system, please try and read it before mailing me. If you don't\n"
BTW. This SIGSEGV/BUS signal handler might be why we haven't seen more
crashers when fuzzing bzip2 directly. That is another reason to
introduce targeted fuzzer entry points.
Cheers,
Mark
next prev parent reply other threads:[~2019-07-11 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard [this message]
2019-01-01 0:00 ` Julian Seward
2019-01-01 0:00 ` 1.0.8 release (Was: [PATCH] Replace project contact email with bzip2-devel@sourceware.org) Mark Wielaard
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=38c77651b5696da99560f36d5285741ca9d1b514.camel@klomp.org \
--to=mark@klomp.org \
--cc=bzip2-devel@sourceware.org \
--cc=jseward@acm.org \
/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).