Out of memory error, Mac 10.6, GnuPG 1.4.10

View: New views
4 Messages — Rating Filter:   Alert me  

Out of memory error, Mac 10.6, GnuPG 1.4.10

by Linus Karlsson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi!

Today I downloaded and compiled GnuPG 1.4.10 to my Mac running Snow  
Leopard. The compilation went smoothly, with no errors (using ./
configure --disable-asm ).

I created a set of new keys, a main key, RSA 4096-bit, and two 2048-
bit subkeys, which I moved to my OpenPGP-card.

I have tried to encrypt two different files with my encryption subkey,  
showing no error. But when I try to decrypt them gpg gives me this  
error:

macbook:Desktop linus$ LANGUAGE=en_US gpg -d test.txt.gpg
gpg: anonymous recipient; trying secret key 01DB6623 ...
gpg(22464) malloc: *** mmap(size=140733193392128) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
gpg: out of  memory while allocating 27 bytes

(The same error is given without the LANGUAGE var, but with the first  
line of the output in Swedish).
The decryption error remains the same regardless if the OpenPGP card  
is inserted in the card reader or not.

However, if I encrypt the file with: gpg -e -a testfile.txt  (with  
ASCII-armoring), the decryption works without any problems.

Has anyone encountered the same error?

Thanks,
Linus

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Re: Out of memory error, Mac 10.6, GnuPG 1.4.10

by David Shaw :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sep 4, 2009, at 9:57 AM, Linus Karlsson wrote:

> Hi!
>
> Today I downloaded and compiled GnuPG 1.4.10 to my Mac running Snow  
> Leopard. The compilation went smoothly, with no errors (using ./
> configure --disable-asm ).

Does it pass 'make check' ?

> I created a set of new keys, a main key, RSA 4096-bit, and two 2048-
> bit subkeys, which I moved to my OpenPGP-card.
>
> I have tried to encrypt two different files with my encryption  
> subkey, showing no error. But when I try to decrypt them gpg gives  
> me this error:
>
> macbook:Desktop linus$ LANGUAGE=en_US gpg -d test.txt.gpg
> gpg: anonymous recipient; trying secret key 01DB6623 ...
> gpg(22464) malloc: *** mmap(size=140733193392128) failed (error  
> code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> gpg: out of  memory while allocating 27 bytes
>
> (The same error is given without the LANGUAGE var, but with the  
> first line of the output in Swedish).
> The decryption error remains the same regardless if the OpenPGP card  
> is inserted in the card reader or not.

Can you run a test without using the card at all?  That is, create the  
main 4096-bit key, and the two 2048-bit subkeys, and encrypt your test  
file in the same way (using --throw-keyid or --hidden-recipient it  
seems), but without transferring the key to the card first.

Something seems wonky in memory allocation (140733193392128 is  
7FFF00001000, which is more than a little suspicious).

If you happen to have a Mac that isn't running Snow Leopard handy, it  
would be great if you could try it there as well.

David


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Re: Out of memory error, Mac 10.6, GnuPG 1.4.10

by Werner Koch :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Fri,  4 Sep 2009 15:57, dt08lk9@... said:

> macbook:Desktop linus$ LANGUAGE=en_US gpg -d test.txt.gpg
> gpg: anonymous recipient; trying secret key 01DB6623 ...
> gpg(22464) malloc: *** mmap(size=140733193392128) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> gpg: out of  memory while allocating 27 bytes

Please run:

  LANGUAGE=en_US gpg --debug 32 -d test.txt.gpg

the last lines of the log might give a hint where we allocate the 27
bytes.  Given that the error is in libc I dount that it will help,
however running it is easy.

Also check that the C macro M_GUARD is not defined:  You find such
#ifdefs in util/memory.c.  Add a line

 #error ooops

inside of such a block and compile it again.  I tested the release on a
64 bit PPC box, so this won't be the problem.


Salam-Shalom,

   Werner

--
Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Re: Out of memory error, Mac 10.6, GnuPG 1.4.10

by Linus Karlsson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks for your answers (both Werner and David). Results follow:

On 4 sep 2009, at 19.34, Werner Koch wrote:
>
> Please run:
>
>  LANGUAGE=en_US gpg --debug 32 -d test.txt.gpg

macbook:Desktop linus$ LANGUAGE=en_US gpg --debug 32 -d testenc.txt.gpg
gpg: reading options from `/Users/linus/.gnupg/gpg.conf'
gpg: DBG: mpi_alloc(2048)
gpg: DBG: mpi_alloc_limb_space(2048)
gpg: DBG: mpi_alloc(4096)
gpg: DBG: mpi_alloc_limb_space(4096)
gpg: DBG: mpi_alloc(64)
gpg: DBG: mpi_alloc_limb_space(64)
gpg: DBG: mpi_alloc(0)
gpg: DBG: free_packet() type=5
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: mpi_alloc(4096)
gpg: DBG: mpi_alloc_limb_space(4096)
gpg: DBG: mpi_alloc(64)
gpg: DBG: mpi_alloc_limb_space(64)
gpg: DBG: mpi_alloc(0)
gpg: DBG: mpi_alloc(4096)
gpg: DBG: mpi_alloc_limb_space(4096)
gpg: DBG: free_packet() type=12
gpg: DBG: mpi_alloc(4096)
gpg: DBG: mpi_alloc_limb_space(4096)
gpg: DBG: free_packet() type=12
gpg: DBG: mpi_alloc(4096)
gpg: DBG: mpi_alloc_limb_space(4096)
gpg: DBG: free_packet() type=12
gpg: DBG: mpi_alloc(2048)
gpg: DBG: mpi_alloc_limb_space(2048)
gpg: DBG: mpi_alloc(64)
gpg: DBG: mpi_alloc_limb_space(64)
gpg: DBG: mpi_alloc(0)
gpg: DBG: mpi_alloc(4096)
gpg: DBG: mpi_alloc_limb_space(4096)
gpg: DBG: free_packet() type=12
gpg: DBG: mpi_alloc(2048)
gpg: DBG: mpi_alloc_limb_space(2048)
gpg: DBG: mpi_alloc(64)
gpg: DBG: mpi_alloc_limb_space(64)
gpg: DBG: mpi_alloc(0)
gpg: DBG: mpi_alloc(4096)
gpg: DBG: mpi_alloc_limb_space(4096)
gpg: DBG: free_packet() type=12
gpg: DBG: mpi_alloc(2048)
gpg: DBG: mpi_alloc_limb_space(2048)
gpg: DBG: mpi_alloc(64)
gpg: DBG: mpi_alloc_limb_space(64)
gpg: DBG: mpi_alloc(0)
gpg: anonymous recipient; trying secret key 01DB6623 ...
gpg(57398) malloc: *** mmap(size=732127585634357248) failed (error  
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
gpg: out of  memory while allocating 27 bytes

>
> Also check that the C macro M_GUARD is not defined:  You find such
> #ifdefs in util/memory.c.  Add a line
>
> #error ooops
>
> inside of such a block and compile it again.

I added #error ooops on line 102 in the specified file. Compilation  
passed without any errors.

On 4 sep 2009, at 19.04, David Shaw wrote:
>
> Does it pass 'make check' ?

Yes, all 27 tests pass.

> Can you run a test without using the card at all?  That is, create  
> the main 4096-bit key, and the two 2048-bit subkeys, and encrypt  
> your test file in the same way (using --throw-keyid or --hidden-
> recipient it seems), but without transferring the key to the card  
> first.

Done, encryption/decryption works fine when I generated new keys  
without moving them to the card.

I tried to create the keys the same way as when I generated them for  
the card, that is, I also removed the main key's secret key from my  
keyring. (Following this guide: https://we.riseup.net/debian/using-the-openpgp-card-with-subkeys 
  ).

I have "hidden-encrypt-to" specified in my gpg.conf, with the key-id  
of the encryption subkey.


> If you happen to have a Mac that isn't running Snow Leopard handy,  
> it would be great if you could try it there as well.

Unfortunatly I only have one Mac, newly formatted to Snow Leopard, so  
I'm afraid I can't test it on any other version.

/Linus

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel