From: | CSN <cool_screen_name90001(at)yahoo(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Function keys cause psql to segfault |
Date: | 2005-09-26 03:03:04 |
Message-ID: | 20050926030304.21033.qmail@web52915.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hmm, all I could think of was perl and php - hitting
F1-4 just caused these chars to be displayed (the
interpreters didn't exit):
^[OP^[OQ^[OR^[OS
CSN
--- Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> Tom Lane wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.
>
> Also, try the function keys in another command-line
> application and see
> if that exits too.
>
> --
> Bruce Momjian |
> http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610)
> 359-1001
> + If your life is a hard drive, | 13 Roberts
> Road
> + Christ can be your backup. | Newtown
> Square, Pennsylvania 19073
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-26 03:10:50 | Re: Function keys cause psql to segfault |
Previous Message | CSN | 2005-09-26 03:00:03 | Re: Function keys cause psql to segfault |