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

psql -c tends to core dump if interrupted

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-bugs(at)postgreSQL(dot)org
Subject: psql -c tends to core dump if interrupted
Date: 2001-03-22 20:28:56
Message-ID: 12320.985292936@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
In current sources, try the following:

while true; do
psql -c "checkpoint" yourdb
done

(any SQL command will do, it needn't be a checkpoint)

Press control-C while it's cycling.  A fair fraction of the time
I get a SEGV coredump from psql.

I've been able to replicate this on both HPUX and LinuxPPC, but I can't
get a useful traceback from either; apparently the stack is trashed.
For example HPUX just gives me

Core was generated by `psql'.
Program terminated with signal 11, Segmentation fault.

#0  0xc0149e14 in ?? () from /usr/lib/libc.1
(gdb) bt
#0  0xc0149e14 in ?? () from /usr/lib/libc.1
Cannot access memory at address 0xffffffac
(gdb)

Anyone else see this?  Can anyone else get a more helpful stack trace?

			regards, tom lane

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2001-03-22 20:41:13
Subject: Re: psql -c tends to core dump if interrupted
Previous:From: Tom LaneDate: 2001-03-22 20:21:49
Subject: Re: bug with identd autentication

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