On Tue, Sep 22, 2020 at 5:40 PM Paul Eggert wrote:
> On 9/22/20 4:40 PM, Jim Meyering wrote:
> > Does anyone know if there's a glibc bug number for it?
>
> I looked for one and didn't find it, so I created glibc bug 26653 for it. See:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26653
Nice
On 9/22/20 5:58 PM, Bruno Haible wrote:
It sounds what you want is a function that returns the stack bounds, in such a
way that every recursion step in a recursive function call the code can ask
"am I close to the stack bound? do I need to stop recursing?"
That shouldn't be necessary, except fo
Hi Paul,
> While looking into this I discovered pthread_getattr_np +
> pthread_attr_getstack
> which might have been nice for the GNU/Linux part of c-stack.c, except
> they're
> not async-signal-safe. As I understand it, libsigsegv works around the
> async-signal-safe problem by parsing /proc
On 9/22/20 4:40 PM, Jim Meyering wrote:
Does anyone know if there's a glibc bug number for it?
I looked for one and didn't find it, so I created glibc bug 26653 for it. See:
https://sourceware.org/bugzilla/show_bug.cgi?id=26653
On Wed, May 27, 2020 at 11:30 PM Norihiro Tanaka wrote:
> On Tue, 26 May 2020 21:14:12 -0700
> "anton.paras" wrote:
>
> > I posted to Stack Exchange, and they recommended that I file a bug. I'd
> > rather not copy+paste it all, so here's the link:
> >
> >
> >
> > https://unix.stackexchange.com/q
Hi Bruce,
> The failing difference isn't whether or not I use gc_pbkdf2_hmac vs.
> gc_pbkdf2_sha1, the failing difference is whether or not I specify the
> crypto/gc-pbkdf2-sha1 module vs. the crypto/gc-pbkdf2 module.
I'm not really familiar with these. Does the libgcrypt documentation help,
ma
Hi Bruno, et al.,
The failing difference isn't whether or not I use gc_pbkdf2_hmac vs.
gc_pbkdf2_sha1, the failing difference is whether or not I specify the
crypto/gc-pbkdf2-sha1 module vs. the crypto/gc-pbkdf2 module. The former
works, the latter does not, with the rest of my project entirel
