> > Running under a debugging malloc library causes a crash earlier on with
> > a double free error on something which is only freed once.
> >
> > Very odd...
> >
> > What platform is this on?
> >
> > Does anyone else get a crash with:
> >
> > openssl ca -infiles xxxx
> 
> Linux: crash
> HP-UX 10.20: no crash when built normally, but with efence:
>   serv01 55: ./openssl ca -infiles xxxx
> 
>   Electric Fence 2.0.1 Copyright (C) 1987-1993 Bruce Perens.
>   Using configuration from /usr/local/ssl/openssl.cnf
>   I am unable to access the ./demoCA/newcerts directory
>   ./demoCA/newcerts: No such file or directory
> 
>   ElectricFence Aborting: free(79e13fe4): address not from malloc().

If for any help. WorkShop dbx implements so called run-time check which
catches things like references to uninitialized and unallocated memory.
Not foolproof, but it might help. Here is what it says:

I am unable to access the ./demoCA/newcerts directory
./demoCA/newcerts: No such file or directory
Read from unallocated (rua):
Attempting to read 4 bytes at address 0x82b43c
    which is 52 bytes before heap block of size 12 bytes at 0x82b470
This block was allocated from:
        [1] default_malloc_ex() at line 79 in "mem.c"
        [2] CRYPTO_malloc() at line 300 in "mem.c"
        [3] lh_insert() at line 193 in "lhash.c"
        [4] prog_init() at line 500 in "openssl.c"
        [5] main() at line 278 in "openssl.c"

Current function is BIO_free_all
  467                   ref=b->references;
(/opt/SUNWspro/bin/../WS6U1/bin/sparcv9/dbx) where
=>[1] BIO_free_all(bio = 0x82b410), line 467 in "bio_lib.c"
  [2] ca_main(argc = 1, argv = 0xffbef2f8), line 1633 in "ca.c"
  [3] do_cmd(prog = 0x82b398, argc = 3, argv = 0xffbef2f0), line 379 in
"openssl.c"
  [4] main(Argc = 3, Argv = 0xffbef2f0), line 298 in "openssl.c"

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to