From: | CSN <cool_screen_name90001(at)yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Function keys cause psql to segfault |
Date: | 2005-09-26 03:00:03 |
Message-ID: | 20050926030003.30729.qmail@web52902.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us> 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.
>
> regards, tom lane
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | CSN | 2005-09-26 03:03:04 | Re: Function keys cause psql to segfault |
Previous Message | Bruce Momjian | 2005-09-26 02:44:18 | Re: Function keys cause psql to segfault |