From: Paul Wise <pabs3@bonedaddy.net>
To: Florian Weimer <fweimer@redhat.com>
Cc: Libc-help <libc-help@sourceware.org>
Subject: Re: is this a bug in glibc or readpst?
Date: Mon, 07 Aug 2023 19:58:21 +0800 [thread overview]
Message-ID: <d82a91ed3dc3a786b2854de5040e968b880a6145.camel@bonedaddy.net> (raw)
In-Reply-To: <87edkfgjno.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Mon, 2023-08-07 at 13:46 +0200, Florian Weimer wrote:
> I expect this is difficult to figure out for certain because of the
> internal stream state may not be very clear unless you are familiar with
> the code. 8-(
I just got confirmation that the same issue is present on Alpine Linux,
which uses the musl libc IIRC and it confirmed with musl-gcc on Debian.
https://paste.debian.net/plainh/47ef35e3/
https://paste.debian.net/1288127/
> So I'd prefer to fix the glibc regression instead.
OK. Given the likely widely varying behaviour in libc implementations,
probably I should also fix the bug in libpst and readpst too.
--
bye,
pabs
https://bonedaddy.net/pabs3/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-08-07 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 2:02 Paul Wise
2022-11-23 8:57 ` Florian Weimer
2022-11-24 0:06 ` Paul Wise
2022-12-02 17:37 ` Florian Weimer
2023-08-06 6:07 ` Paul Wise
2023-08-07 8:59 ` Florian Weimer
2023-08-07 11:00 ` Paul Wise
2023-08-07 11:46 ` Florian Weimer
2023-08-07 11:58 ` Paul Wise [this message]
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=d82a91ed3dc3a786b2854de5040e968b880a6145.camel@bonedaddy.net \
--to=pabs3@bonedaddy.net \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.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).