Search Postgresql Archives

Re: Function keys cause psql to segfault

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I did 'strace psql dbname' and this was the output
after hitting F1:

read(0, "\33", 1)                       = 1
read(0, "O", 1)                         = 1
read(0, "P", 1)                         = 1
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++


CSN

--- Tom Lane <tgl@xxxxxxxxxxxxx> wrote:

> Bruce Momjian <pgman@xxxxxxxxxxxxxxxx> writes:
> > CSN wrote:
> >> If I'm in psql (via putty, from WinXP to Redhat)
> and
> >> hit F1-4 (F5+ just display a ~), psql will
> >> segmentation fault and exit.
> 
> > My guess is that those send a break or some
> control sequence.  od -c
> > might show you what is being output.
> 
> Try watching the psql process with strace in another
> terminal window.
> If Bruce's theory is correct (and it sounds good to
> me) then you should
> be able to see a signal being delivered to psql.
> 
> 			regards, tom lane
> 



		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux