> On Tue, Sep 21, 2010 at 10:45 AM, Bryan Murphy <bmurphy1976@xxxxxxxxx>wrote: > >> I'm sorry, when I went back over to double check my steps I realized I ran >> the wrong command. I am *still* having the problem. It appears that the >> MD5 hashes now match, but it's still failing. I have postgres and pgpool >> installed in /opt/postgresql, but I have the same problem when I put >> pool_passwd in /etc and /opt/postgresql/etc. >> > > Here is a gdb backtrace from the child process when it sigsegs after I enter > the correct password. I'm digging in a little deeper now and I thought this > might be useful. Unfortunately the gdb backtrace does not show enough information because of optimization, I guess. Can you take a backtrace with optimization disabled binary? You can obtain this by editing Makefile around line 147. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > (gdb) bt > #0 0xefcbf24f in ?? () > #1 0x08052ac5 in do_md5 (backend=0xefcbf24f, frontend=0x9dfc5c0, > reauth=<value optimized out>, protoMajor=3) > at /usr/include/bits/string3.h:52 > #2 0x08052e7b in pool_do_auth (frontend=0x9df97c0, cp=0x9df8fa8) at > pool_auth.c:222 > #3 0x080509a9 in connect_backend (unix_fd=4, inet_fd=5) at child.c:1143 > #4 do_child (unix_fd=4, inet_fd=5) at child.c:293 > #5 0x0804bbdf in fork_a_child (unix_fd=4, inet_fd=5, id=<value optimized > out>) at main.c:1024 > #6 0x0804ddef in main (argc=3, argv=0xbfab6754) at main.c:514 > > >> >> -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
