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
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 di
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
> --- SIG
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 ...
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 wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > CSN wrote:
> > >> If I'm in psql (via putty, from WinXP to
> Redh
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 <[EMA
Tom Lane wrote:
> Bruce Momjian 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
Bruce Momjian 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
Here's what 'od -c' shows for F1-4:
^[OP^[OQ^[OR^[OS
CSN
--- Bruce Momjian 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 function keys
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
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 WinX
Daniel Verite wrote:
> Bruce Momjian wrote:
>
> > Is there a problem with a DLL writing to a file descriptor opened by
> > application code? I would think not, but perhaps.
>
> After some more testing, I've found out that it works only if the
> application code uses the shared version of t
Bruce Momjian wrote:
> Is there a problem with a DLL writing to a file descriptor opened by
> application code? I would think not, but perhaps.
After some more testing, I've found out that it works only if the
application code uses the shared version of the C library
(msvcrt.dll)
That me
How do you know the delay isn't in the client's lookup of the server?
You are absolutely right!
I am using the ip address to connect to, so I thougt that was it.
But the client is doing netbios queries seen with ethereal.
Thanks to both of you.
Poul
---(end of
14 matches
Mail list logo
