PRNG not seeded => Seg.Fault

From: Stephen Pillinger <S(dot)M(dot)Pillinger(at)cs(dot)bham(dot)ac(dot)uk>
To: pgsql-bugs(at)postgresql(dot)org
Subject: PRNG not seeded => Seg.Fault
Date: 2001-11-08 16:04:55
Message-ID: E161rff-0000VZ-00@emily.cs.bham.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Hi there,
I think I may have discovered a minor but annoying bug in PostgreSQL.

PostgreSQL version 7.1.3
with openssl-0.9.6b
readline-4.2

Compiled under Solaris 8 with SPARCWorks compiler.

Started with command:

postmaster -D /export/pgsql/data -i -l

Attempting to connect via an SSL aware psql client machine that doesn't
have a PRNG seed causes the backend to generate a Segmentation Fault.

A little digging around found to culprit in

src/backend/postmaster/postmaster.c @ line 1115

the ERR_reason_error_string(ERR_get_error()) in the fprintf statement.

Remove it from the fprintf and all works fine.

Apart from that PostgreSQL is great!

Many thanks,

Steve

---------------------------------------------------------------------------
Stephen Pillinger | School of Computer Science,
Senior Computer Officer | The University of Birmingham,
E-Mail: S(dot)M(dot)Pillinger(at)cs(dot)bham(dot)ac(dot)uk | Edgbaston,
Tel: 0121-414 3214 Fax: 0121-414 4281 | Birmingham B15 2TT, UK.
+-------------------------------------------------------------------------+

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Frank McKenney 2001-11-08 23:09:59 Perl script failure => Postgres 7.1.2 database corruption
Previous Message Hans-Jürgen Schönig 2001-11-08 15:40:20 Bug in 7.1.3 and 7.2?