Building on OS X Lion
dshaw at jabberwocky.com
Tue Jul 26 05:22:10 CEST 2011
On Jul 25, 2011, at 4:58 PM, Nicholas Cole wrote:
> On Mon, Jul 25, 2011 at 5:10 PM, David Shaw <dshaw at jabberwocky.com> wrote:
>> On Jul 25, 2011, at 11:40 AM, Nicholas Cole wrote:
>>> On Mon, Jul 25, 2011 at 4:38 PM, Nicholas Cole <nicholas.cole at gmail.com> wrote:
>>>> On Mon, Jul 25, 2011 at 11:31 AM, Nicholas Cole <nicholas.cole at gmail.com> wrote:
>>>>> Dear List,
>>>>> Building 1.4.11 on OS X Lion (Intel Core 2 Duo) fails with the following error:
>>>>> Is this a known problem?
>>>> My mistake - I think I might have had some 3rd party libraries
>>>> confusing the build process!
>>> But a rebuilt gpg is still failing with this error:
>>> nicholas$ gpg --card-status
>>> gpg(97903) malloc: *** mmap(size=2608166010582208512) failed (error code=12)
>>> *** error: can't allocate region
>>> *** set a breakpoint in malloc_error_break to debug
>>> gpg: out of memory while allocating 26 bytes
>> Interesting. 2608166010582208512 in binary is 10010000110010000100010010101100000000000000000001000000000000. Looks like the lower 32 bits are correct (being equal to 4096, which makes sense in this context), but the upper 32 bits are uninitialized or otherwise mangled.
>> I haven't upgraded to Lion yet, so I can't easily run this myself, but can you get a backtrace via gdb? Just run gpg under gdb, and "break malloc_error_break", then "run --card-status". It'll stop at the breakpoint, and you can then do "bt full".
> Dear David,
> I hope that the following output is useful!
Werner spotted it earlier. This looks like a 32-bit/64-bit mismatch between gpg and pcsc. It's an open bug at https://bugs.gnupg.org/gnupg/issue1358
More information about the Gnupg-devel