Postgres Pro
Downloads
Home   >   mailing lists

Thread: BUG #5631: psql dumps core during command editing

BUG #5631: psql dumps core during command editing

From
"David Kensiski"
Date:
The following bug has been logged online:

Bug reference:      5631
Logged by:          David Kensiski
Email address:      David@Schoolloop.com
PostgreSQL version: 8.4
Operating system:   Solaris 10
Description:        psql dumps core during command editing
Details:

The psql binary (64-bit from binary install) dumps core when I attempt to
edit the input line after a few characters are entered:

tombu@i2:~$ psql homerdb
psql (8.4.4)
Type "help" for help.

homerdb=# abcde(Ctrl-A)Segmentation Fault (core dumped)

Note that "abcd(Ctrl-A)" doesn't result in a Seg Fault, though
"abcde(Ctrl-A)" does.

Here's the tail end of a truss of the psql process:

read(0, " d", 1)                                = 1
write(1, " d", 1)                               = 1
read(0, " e", 1)                                = 1
write(1, " e", 1)                               = 1
read(0, "01", 1)                                = 1
    Incurred fault #6, FLTBOUNDS  %pc = 0xFFFFFD7FFEF087C2
      siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFFFEF2D500
    Received signal #11, SIGSEGV [default]
      siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFFFEF2D500

Alas, I'd give you a backtrace, but I'm running the 64-bit binary and only
have a 32-bit gdb.

Re: BUG #5631: psql dumps core during command editing

From
Tom Lane
Date:
"David Kensiski" <David@Schoolloop.com> writes:
> The psql binary (64-bit from binary install) dumps core when I attempt to
> edit the input line after a few characters are entered:

This most likely indicates a problem with the libreadline or libedit
library you're using.

            regards, tom lane

Re: BUG #5631: psql dumps core during command editing

From
David L Kensiski
Date:
I though of that, but it's linked into the binary.  Maybe this is a
problem with the Sun build and not the code?  How do I get in touch
with the build maintainer?

--Dave



tombu@i2:~$ /usr/ccs/bin/nm -o /usr/postgres/current/bin/64/psql |
grep readline
[542]   |0000000020547260|0000000000000072|FUNC |GLOB |0    |12     |
initialize_readline
[924]   |0000000020676600|0000000000000610|FUNC |GLOB |0    |12     |
readline
[306]   |0000000000000000|0000000000000000|FILE |LOCL |0    |ABS    |
readline.c
[834]   |0000000022164570|0000000000000004|OBJT |GLOB |0    |19     |
readline_echoing_p
[866]   |0000000022165210|0000000000000010|OBJT |GLOB |0    |19     |
rl_readline_name



On Aug 27, 2010, at 9:38 PM, Tom Lane wrote:

> "David Kensiski" <David@Schoolloop.com> writes:
>> The psql binary (64-bit from binary install) dumps core when I
>> attempt to
>> edit the input line after a few characters are entered:
>
> This most likely indicates a problem with the libreadline or libedit
> library you're using.
>
>             regards, tom lane

Re: BUG #5631: psql dumps core during command editing

From
Bruce Momjian
Date:
David L Kensiski wrote:
> I though of that, but it's linked into the binary.  Maybe this is a
> problem with the Sun build and not the code?  How do I get in touch
> with the build maintainer?

Is there a README in the build install somewhere?

---------------------------------------------------------------------------


>
> --Dave
>
>
>
> tombu@i2:~$ /usr/ccs/bin/nm -o /usr/postgres/current/bin/64/psql |
> grep readline
> [542]   |0000000020547260|0000000000000072|FUNC |GLOB |0    |12     |
> initialize_readline
> [924]   |0000000020676600|0000000000000610|FUNC |GLOB |0    |12     |
> readline
> [306]   |0000000000000000|0000000000000000|FILE |LOCL |0    |ABS    |
> readline.c
> [834]   |0000000022164570|0000000000000004|OBJT |GLOB |0    |19     |
> readline_echoing_p
> [866]   |0000000022165210|0000000000000010|OBJT |GLOB |0    |19     |
> rl_readline_name
>
>
>
> On Aug 27, 2010, at 9:38 PM, Tom Lane wrote:
>
> > "David Kensiski" <David@Schoolloop.com> writes:
> >> The psql binary (64-bit from binary install) dumps core when I
> >> attempt to
> >> edit the input line after a few characters are entered:
> >
> > This most likely indicates a problem with the libreadline or libedit
> > library you're using.
> >
> >             regards, tom lane
>

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +