conflict between Crypto++ 5.6.0 and GNU binutils 2.19.91.20091014-0ubuntu1
Zooko O'Whielacronx
2.19.91.20091006-0ubuntu1 to 2.19.91.20091014-0ubuntu1 this broke the
build of Crypto++ 5.6.0 in such a way that building Crypto++ with the
new binutils results in indefinite hangs with max CPU usage or seg
faults. Here is the bug report at launchpad which includes the
history of me figuring out exactly which version of which tool
introduced this change and also has links to the pycryptopp buildbot
which shows Crypto++ 5.6.0 as built with the new binutils getting a
segfault. The buildbot also has a valgrind report. The launchpad
ticket also has links to the diffs between the most recent succeeding
version of binutils and the earliest failing version, but I don't know
enough about binutils to spot the problem.
If someone out there knows how to help, that would be great. In the
meantime, at least be aware that you shouldn't upgrade to Ubuntu 9.10
(due to be released tomorrow) if you want to build Crypto++ 5.6.0!
Regards,
Zooko
zooko
platform and it is not known if it affects other platforms.
Wei Dai
have no idea what the (fairly large) binutil patch is doing. How can we find
out who submitted the the binutil patch and contact him or her?
I can also look at this in the debugger and see if I can fix it in Crypto++
code. Can you either give me a shell account on a machine that can reproduce
this, or tell me how to reproduce this, starting with a blank VMware
instance?
Until this is fixed, you can try to work around it by disabling the SHA256
(or all) assembly code.
--------------------------------------------------
From: "Zooko O'Whielacronx" <zoo...@gmail.com>
Sent: Tuesday, October 27, 2009 8:21 AM
To: "Wei Dai" <wei...@weidai.com>
Subject: Re: conflict between Crypto++ 5.6.0 and GNU binutils
2.19.91.20091014-0ubuntu1
> On Mon, Oct 26, 2009 at 9:08 PM, Wei Dai <wei...@weidai.com> wrote:
>> Link to the bug report?
>
> Whoops, sorry about that:
>
> https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303
>
zooko
> The error is clearly occurring within the SHA256 inline assembly code. But I
> have no idea what the (fairly large) binutil patch is doing. How can we find
> out who submitted the the binutil patch and contact him or her?
asking that question. I suppose the patch came from "upstream"
binutils, i.e. the Ubuntu folks acquired the patch from the binutils
folks, but I'm not sure how to trace its exact provenance.
> I can also look at this in the debugger and see if I can fix it in Crypto++
> code. Can you either give me a shell account on a machine that can reproduce
> this, or tell me how to reproduce this, starting with a blank VMware
> instance?
Install Ubuntu Karmic Koala (release candidate or final release)
Get the Crypto++ 5.6.0 source code
run "make"
run "cryptest.exe v"
> Until this is fixed, you can try to work around it by disabling the SHA256
> (or all) assembly code.
test the version of the GNU assembler and disable ASM if it is the
known-bad version.
Zooko O'Whielacronx
which exactly patch to GNU assembler causes the problem:
Wei Dai
get into the Ubuntu release, or into an update shortly after. Let me know if
I still need to do anything.
Sent: Tuesday, October 27, 2009 7:22 PM
To: "Crypto++ Users" <cryptop...@googlegroups.com>
2.19.91.20091014-0ubuntu1
>