Re: Function keys cause psql to segfault

From: CSN <cool_screen_name90001(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Function keys cause psql to segfault
Date: 2005-09-26 03:34:01
Message-ID: 20050926033401.37621.qmail@web52914.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


It looks like I had readline 4.3 installed. I just
installed readline 5.0 - the F1-4 keys still cause
psql to segfault. (AFAIK I don't need to recompile
postgres for psql to use the newly installed
readline).

CSN

--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> CSN <cool_screen_name90001(at)yahoo(dot)com> writes:
> > 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) ---
>
> Hmm ... I don't have an F1 key, but I typed
> escape-O-P at a psql
> running under Linux, and got this:
>
> Process 28978 attached - interrupt to quit
> read(0, "\33", 1) = 1
> read(0, "O", 1) = 1
> read(0, "P", 1) = 1
> write(2, "\7", 1) = 1
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> read(0,
>
> So it seems fine here. I'm wondering if there's
> something broken
> about your machine's readline library.
>
> regards, tom lane
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message CSN 2005-09-26 03:41:46 Re: Function keys cause psql to segfault
Previous Message Klint Gore 2005-09-26 03:23:18 Re: Function keys cause psql to segfault