Alejandro Colomar

In , I've been developing a set of macros that wrap strtol(3) et al. to do numeric parsing safely: And wrote a library, hosted in .

> I don't think we should check the calls of sscanf on the result of a successful regex match. > Failing to parse those would indicate an error in the...

> Honestly, I don't think ENOMEM in sscanf is a realistic scenario (nowadays). But sure, let's take a **nodiscard** approach everywhere, if that's what we want to focus on. >...

> 3. Future: Consider using liba2i I hope to get it packaged into the first distributions during this year or the next, although it depends on how much time it...

> that chain of logic makes no sense. the f*() functions can fail if they cannot allocate a buffer. > sscanf does not allocate buffers. I see the following on...

Can you please paste screenshots of the problem, to make sure I understand it? I think I know what you mean, but am not sure. I can try to debug...

I assume those red thingies are 3 different emails? Or are they the same?

Does it happen only with some keys, or with all of them? Do you notice any pattern in when/how it happens? Do you use autocrypt? What is your gpgme version?...

And does it happen in other systems with the same keys?

Are you able to run (old) mutt(1) on that system? And does it reproduce the issue?