Unable to compile GnuPG 2.1 beta 3

[Alphazo]

Was my backtrace of any help regarding the seg. fault I'm experiencing?

On Wed, Dec 21, 2011 at 9:36 PM, Alphazo <alphazo at gmail.com> wrote:
> here is the backtrace:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff732e700 in ?? () from /lib/libgcrypt.so.11
> (gdb) bt full
>
> #0  0x00007ffff732e700 in ?? () from /lib/libgcrypt.so.11
> No symbol table info available.
> #1  0x00007ffff72e6726 in ?? () from /lib/libgcrypt.so.11
> No symbol table info available.
> #2  0x00007ffff72e7bfa in ?? () from /lib/libgcrypt.so.11
> No symbol table info available.
> #3  0x00007ffff72e1ef2 in gcry_sexp_build () from /lib/libgcrypt.so.11
> No symbol table info available.
> #4  0x0000000000425f7a in ?? ()
> No symbol table info available.
> #5  0x000000000043703f in ?? ()
> No symbol table info available.
> #6  0x000000000043833d in ?? ()
> No symbol table info available.
> #7  0x0000000000438867 in ?? ()
> No symbol table info available.
> #8  0x000000000040b19d in ?? ()
> No symbol table info available.
> #9  0x00007ffff6b6114d in __libc_start_main () from /lib/libc.so.6
> No symbol table info available.
> #10 0x000000000040c5ed in ?? ()
> No symbol table info available.
> #11 0x00007fffffffe0b8 in ?? ()
> No symbol table info available.
> #12 0x00000000ffffffff in ?? ()
> No symbol table info available.
> #13 0x0000000000000003 in ?? ()
> No symbol table info available.
> #14 0x00007fffffffe40f in ?? ()
> No symbol table info available.
> #15 0x00007fffffffe41d in ?? ()
> No symbol table info available.
> #16 0x00007fffffffe420 in ?? ()
> No symbol table info available.
> #17 0x0000000000000000 in ?? ()
> No symbol table info available.
>
>
> On Wed, Dec 21, 2011 at 7:03 PM, Werner Koch <wk at gnupg.org> wrote:
>> On Wed, 21 Dec 2011 15:19, alphazo at gmail.com said:
>>
>>> However I also received a seg. fault at the end:
>>>
>>> gpg: signal Segmentation fault caught ... exiting
>>> [1]    10610 segmentation fault  gpg2 -v --list-keys
>>>
>>> Is this normal?
>>
>> Definitely no.  Segfaults are bugs.  Can you run it unter gdb and send a
>> backtrace?
>>
>>  gdb gpg2
>>  gdb> run  -v --list-keys
>>  gdb> # after it stops at the segv
>>  gdb> bt full
>>
>>
>> Shalom-Salam,
>>
>>   Werner
>>
>> --
>> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
>>