elein <[EMAIL PROTECTED]> writes:
> I'll verify I have the version I think I have...
> (gdb) bt
> #0 0x0805dd15 in trim_trailing_separator (path=0x0) at path.c:442
> #1 0x0805d6b2 in canonicalize_path (path=0x0) at path.c:123
> #2 0x0804af80 in exec_command (cmd=0x808f958 "e", scan_state=0x808b
This is the source for beta2. Perhap the previous
fix was to add the path[0] check but the path == NULL
check was forgotten?
OR, is it a problem if path==NULL?
--elein
On Mon, Sep 13, 2004 at 01:31:26PM -0700, elein wrote:
> This looks like the same bug as Michael's
> http://archives.postgresql
This looks like the same bug as Michael's
http://archives.postgresql.org/pgsql-bugs/2004-08/msg00103.php
trim_directory needs to check for a NULL pointer in path.
if ( path == NULL || path[0] == '\0' )
I'll verify I have the version I think I have...
(gdb) bt
#0 0x0805dd15 in trim_trai
elein <[EMAIL PROTECTED]> writes:
> Has anyone else experienced a segfault in psql on 8.0B2
> when using \e? I can reproduce this consistently.
Hmm, we fixed a bug in \e not long ago, but it was pre-beta2 ...
regards, tom lane
---(end of broadcast
On Mon, Sep 13, 2004 at 12:47:54PM -0700, elein wrote:
> Has anyone else experienced a segfault in psql on 8.0B2
> when using \e? I can reproduce this consistently.
>
> If not I'll trace it down if I can, but if it is a known
> problem, I won't bother.
I'm using the latest CVS sources on Solaris
On Mon, Sep 13, 2004 at 12:47:54PM -0700, elein wrote:
> Has anyone else experienced a segfault in psql on 8.0B2
> when using \e? I can reproduce this consistently.
I do it all the time and I haven't seen it ... is your query too long or
something? Care to show psql's backtrace?
--
Alvaro Herr
Has anyone else experienced a segfault in psql on 8.0B2
when using \e? I can reproduce this consistently.
If not I'll trace it down if I can, but if it is a known
problem, I won't bother.
--elein
[EMAIL PROTECTED]Varlena, LLC
