24 Jul 2003 12:26:17 -0000
Yes, I meant v1.1.12, sorry.
I'm not sure what I did to cause this--it came from somewhere deep in my code and I don't have time to rip it apart.
However, I don't think its my code's fault as it seems to be a transient bug. I've ran into a few of these within libgcrypt over the last few months.
If you can fix this problem, then great. If not, I'll probably end up examining it eventually--I'm just not sure if that can be anytime soon.
This message has been sent via an anonymous mail relay at www.no-id.com.