As far as the configure options -- Originally, they were merely --with-perl and --with-python, but just to rule out problems there, I've since just been going with a straight compile (not additional options).
I will get the backtrace, etc. within the next hour or so. Thanks! - Matt Quoting Craig Ringer <cr...@postnewspapers.com.au>: > On 03/02/11 11:11, Matt Zinicola wrote: > > OK, it doesn't seem to be a simple problem of linking to the wrong > library then. psql is linking to the correct libpq. initdb isn't linking > to anything much at all, but still crashes for no apparent reason. > Something else may be going on. Please supply the full command line you > used to "./configure" when compiling postgres. If you're not sure what > it was, you can find it in the top of "config.log" in your compile > directory. > > Is there any chance you can get us a backtrace of one of the crashing > programs? Try this: > > gdb --args psql > > Once it loads, it'll drop you to a > > (gdb) > > prompt. Enter "run" then press enter. > > (gdb) run > > Psql will then load for a while, crash, and drop you back to a (gdb) > prompt after printing out a message like: > > Program received signal SIGSEGV, Segmentation fault. > > Enter the "bt" command at the (gdb) prompt and press enter. > > (gdb) bt > > ... then copy and paste everything from "gdb --args psql" through to the > end of the output printed by "bt", put it on http://pastebin.com/ and > send a link to that in your reply email here. > > I've created a sample to give you the idea, by starting psql then > intentionally crashing it by sending it a manual SIGSEGV. See: > > http://pastebin.com/b8D9i2tb > > > -- > System & Network Administrator > POST Newspapers > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
