Skip site navigation (1) Skip section navigation (2)

Re: ECPG failure on BF member Vaquita (Windows Vista)

From: "Mark Wong" <markwkm(at)gmail(dot)com>
To: "Michael Meskes" <meskes(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG failure on BF member Vaquita (Windows Vista)
Date: 2007-04-25 16:26:10
Message-ID: 70c01d1d0704250926h7e534776qb1bfb838ae3fdc47@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 4/25/07, Michael Meskes <meskes(at)postgresql(dot)org> wrote:
> I also saw that wombat is segfaulting in ecpg tests but not only with
> CVS HEAD but also trying to test 8.2. Any idea what's going on with this
> machine?

I generated a stack trace for REL8_2_STABLE, but I'm not sure how
helpful it is.  Let me know what other information I can provide...
Looks like I don't have symbols for libc.

Core was generated by `sql/update '.
Program terminated with signal 11, Segmentation fault.
#0  ECPGget_variable (ap=<value optimized out>, type=<value optimized out>,
    var=0x10028730, indicator=1 '\001') at execute.c:131
131                             var->ind_value = *((char **)
(var->ind_pointer));
(gdb) bt
#0  ECPGget_variable (ap=<value optimized out>, type=<value optimized out>,
    var=0x10028730, indicator=1 '\001') at execute.c:131
#1  0x0000040000048948 in ECPGdo (lineno=28, compat=<value optimized out>,
    force_indicator=<value optimized out>,
    connection_name=<value optimized out>, query=<value optimized out>)
    at execute.c:195
#2  0x0000000010000d20 in main (argc=<value optimized out>,
    argv=<value optimized out>) at update.pgc:28
#3  0x000004000063ce4c in .generic_start_main () from /lib/libc.so.6
#4  0x000004000063d0f8 in .__libc_start_main () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()


Regards,
Mark

In response to

Responses

pgsql-hackers by date

Next:From: Steve CrawfordDate: 2007-04-25 16:36:35
Subject: Re: Vacuum-full very slow
Previous:From: Alvaro HerreraDate: 2007-04-25 16:13:57
Subject: Re: Vacuum-full very slow

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group