Thanks Tom, We don't have gdb. We have mdb and pstack. From the core: [root@udrv] # mdb /opt/postgres/8.3-community/bin/postmaster /root/core Loading modules: [ libc.so.1 ld.so.1 ] > ::status debugging core file of postmaster (32-bit) from udrv file: /opt/postgres/8.3-community/bin/postmaster initial argv: /opt/postgres/8.3-community/bin/postmaster -F threading model: multi-threaded status: process terminated by SIGSEGV (Segmentation Fault) > ::regs %cs = 0x003b %eax = 0x083b7fe0 %ds = 0x0043 %ebx = 0x00000000 %ss = 0x0043 %ecx = 0x00000000 %es = 0x0043 %edx = 0x00000000 %fs = 0x0000 %esi = 0x00000001 %gs = 0x01c3 %edi = 0x00000005 %eip = 0x081a8562 ConnCreate+0xb6 %ebp = 0x08047c88 %kesp = 0x00000000 %eflags = 0x00010206 id=0 vip=0 vif=0 ac=0 vm=0 rf=1 nt=0 iopl=0x0 status=<of,df,IF,tf,sf,zf,af,PF,cf> %esp = 0x08047c78 %trapno = 0xe %err = 0x6 [root@udrv] # pstack /root/core core '/root/core' of 771: /opt/postgres/8.3-community/bin/postmaster -F 081a8562 ConnCreate (5) + b6 081a791b ServerLoop (8047e68, 83b7930, 2, fead58be, 8047e68, 83c28b8) + db 081a73f1 PostmasterMain (2, 83b7930) + ab5 08164e3a main (2, 8047e44, 8047e50) + 17a 080891fa _start (2, 8047ed0, 8047efb, 0, 8047efe, 8047f2e) + 7a > Sam -----Original Message----- From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] Sent: Friday, 10 December 2010 2:17 PM To: Samuel Stearns Cc: Shoaib Mir; pgsql-admin@xxxxxxxxxxxxxx Subject: Re: Postgres Crash Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx> writes: > Tom, no useful messages in the log prior. I do have a 47M core dump. What should I do with that? If you use gdb, try $ gdb /path/to/postmaster /path/to/corefile gdb> bt ... useful info here ... gdb> quit I think the preferred debugger on Solaris might not be gdb, but if so you'll need to consult its docs to find out how to get a stack trace. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
