Re: Function keys cause psql to segfault - Mailing list pgsql-general

From CSN
Subject Re: Function keys cause psql to segfault
Date
Msg-id 20050926030003.30729.qmail@web52902.mail.yahoo.com
Whole thread Raw
In response to Re: Function keys cause psql to segfault  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Function keys cause psql to segfault
Re: Function keys cause psql to segfault
List pgsql-general
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@sss.pgh.pa.us> wrote:

> Bruce Momjian <pgman@candle.pha.pa.us> 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

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Function keys cause psql to segfault
Next
From: CSN
Date:
Subject: Re: Function keys cause psql to segfault