vasprintf core dump problem on Solaris 2.8

[Marcus Brinkmann]

Hello,

On Wed, Aug 07, 2002 at 11:40:52AM -0400, Andrzej Cuper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> I'm running into core dump problems with test programs
> t-encrypt, t-decrypt etc, when runing 'make check'
> (on Solaris 2.8). The problem seems to be with
> vasprintf (vasprintf.c in gpgme directory) implementation
> and more specifically with the following fragment of code.
> Also enclosed call stack from gdb. Please help!

The vasprintf implementation seems to be difficult to make portable.
Which version have you tried?  Please try the version from CVS after the
following change in gpgme/:

2002-07-25  Marcus Brinkmann  <marcus@g10code.de>

        * Makefile.am (libgpgme_la_LDADD): Add @LIBOBJS@ for vasprintf and
        fopencookie.
        * vasprintf.c: Update to more recent libiberty version.
        * debug.h: Replace #elsif with #elif.
 
> Also, can somebody explain the use of
>  DEBUG_BEGIN, DEBUG_ADD1, DEBUG_END.
>  Do I need to set up some environemnt
> variable to be able to see this. Which file does it go to?

If you set the environment variable GPGME_DEBUG=1 (or 2 or 3),
it will print out debug info on stderr.  To make it go into a
file, you use GPGME_DEBUG=1:/tmp/gpgme.debug, or similar.
However, only some cryptic information about the internal communication with
gpg is printed.

Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    marcus@gnu.org
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/