Douglas McNaught wrote:
CSN [EMAIL PROTECTED] writes:
Hmm, in putty (Terminal-Keyboard) I changed the
function keys and keypad from ESC[n~ to Linux.
Hitting F1-5 in psql outputs ABCDE - no segfaults!
Setting it to Xterm R6 also results in function keys
1-4 causing segfaults (there are also
CSN [EMAIL PROTECTED] writes:
Hmm, in putty (Terminal-Keyboard) I changed the
function keys and keypad from ESC[n~ to Linux.
Hitting F1-5 in psql outputs ABCDE - no segfaults!
Setting it to Xterm R6 also results in function keys
1-4 causing segfaults (there are also options for
VT400,
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. Not that I'm in the habit
of entering function keys while in psql - I
accidentally hit one while entering numbers (lost a
fair amount of history).
I just tried it using
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. Not that I'm in the habit
of entering function keys while in psql - I
accidentally hit one while entering numbers (lost a
fair amount of history).
My guess
Here's what 'od -c' shows for F1-4:
^[OP^[OQ^[OR^[OS
CSN
--- Bruce Momjian pgman@candle.pha.pa.us wrote:
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. Not that I'm in the
habit
of entering
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
Tom Lane 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
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 [EMAIL
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@candle.pha.pa.us wrote:
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
CSN wrote:
If I'm in
CSN [EMAIL PROTECTED] 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
On Sun, 25 Sep 2005 20:00:03 -0700 (PDT), CSN [EMAIL PROTECTED] wrote:
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
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 [EMAIL PROTECTED] wrote:
CSN [EMAIL PROTECTED] writes:
I did
Hmm, in putty (Terminal-Keyboard) I changed the
function keys and keypad from ESC[n~ to Linux.
Hitting F1-5 in psql outputs ABCDE - no segfaults!
Setting it to Xterm R6 also results in function keys
1-4 causing segfaults (there are also options for
VT400, VT100+, and SCO - haven't tried those).
13 matches
Mail list logo
