Skip site navigation (1) Skip section navigation (2)

segfault in psql on x86_64

From: Orion Henry <orion(at)trustcommerce(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: segfault in psql on x86_64
Date: 2004-01-30 23:35:14
Message-ID: 1075505714.24390.54.camel@orthanc (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
I am running vanilla Fedora Core 1 - test1 for x86_64
running an update system running kernel 2.4.22-1.2166.nptlsmp
The system is a dual opteron pogolinux box with 512M and a IDE RAID 1
from 3ware

I downloaded postgresql-7.4.1-1PGDG.src.rpm
and built it on the system. (rpmbuild --rebuild ...)
and installed the resulting RPM's.  

The database starts and stops normally on install

The psql tool ( as well as createuser/vacuum etc all seg fault)

It appears to be faulting on a kerberos call which is odd because I
don't use kerberos for anything.

Here everything plus a gdb backtrace.

[root(at)bree data]# psql
Segmentation fault
[root(at)bree data]# gdb psql
GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "x86_64-redhat-linux-gnu"...Using host
libthread_db library "/lib64/tls/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/psql
[Thread debugging using libthread_db enabled]
[New Thread 182894073344 (LWP 5363)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 182894073344 (LWP 5363)]
0x0000003de59010e0 in ?? () from /lib64/tls/libm.so.6
(gdb) bt
#0  0x0000003de59010e0 in ?? () from /lib64/tls/libm.so.6
#1  0x0000003de6e16c61 in krb5int_initialize_library () from
/usr/lib64/libkrb5.so.3
#2  0x0000003de6e413fb in krb5_init_secure_context () from
/usr/lib64/libkrb5.so.3
#3  0x0000003e2d40844e in pg_krb5_init (PQerrormsg=0x7fbfffda50 "
�\177") at fe-auth.c:291
#4  0x0000003e2d4085a9 in pg_krb5_authname (PQerrormsg=0x3de6f6bc80
"4�") at fe-auth.c:348
#5  0x0000003e2d408ce1 in fe_getauthname (PQerrormsg=0x7fbfffda50 "
�\177") at fe-auth.c:731
#6  0x0000003e2d40af56 in conninfo_parse (conninfo=0x5320c0 "uA->",
errorMessage=0x529db0) at fe-connect.c:2720
#7  0x0000003e2d408db8 in connectOptions1 (conn=0x529a20,
conninfo=0x3de6f6bc80 "4�") at fe-connect.c:328
#8  0x0000003e2d4091e3 in PQsetdbLogin (pghost=0x0, pgport=0x0,
pgoptions=0x0, pgtty=0x0, dbName=0x0, login=0x0, pwd=0x0)
    at fe-connect.c:541
#9  0x000000000040a1db in main (argc=1, argv=0x7fbfffe058) at
startup.c:183
(gdb)


-- 
Orion Henry <orion(at)trustcommerce(dot)com>

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2004-01-31 00:04:03
Subject: Re: Question about indexes
Previous:From: Hannu KrosingDate: 2004-01-30 23:21:42
Subject: Re: Question about indexes

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-01-31 00:56:51
Subject: Re: initdb: directory not empty issue
Previous:From: Kris JurkaDate: 2004-01-30 20:12:44
Subject: Re: Why not (OID) in JDeveloper10g?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group