| From: | "Mark Wong" <markwkm(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "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 18:54:38 |
| Message-ID: | 70c01d1d0704251154w4678e1b1m8fa6c0cb152a6d61@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/25/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > I think you'll need to compile with optimisation turned off and then try
> > running the test under debugger control, putting a breakpoint in
> > ECPGget_variable() and then stepping through it. I wonder what value of
> > var->ind_pointer it is getting?
>
> You could probably inspect the contents of *var in that dump without
> having to recompile. Given that this is PPC64, I'm betting on a pointer
> size or alignment problem ...
Does this help?
(gdb) p var->type
$1 = 4267828624
(gdb) p var->value
$2 = (void *) 0x1
(gdb) p var->pointer
$3 = (void *) 0x1
(gdb) p var->varcharsize
$4 = 3
(gdb) p var->arrsize
$5 = 4
(gdb) p var->offset
$6 = 29
(gdb) p var->ind_type
$7 = 0
(gdb) p var->ind_pointer
$8 = (void *) 0x0
(gdb) p var->ind_varcharsize
$9 = 0
(gdb) p var->ind_arrsize
$10 = 0
(gdb) p var->ind_offset
$11 = 5
(gdb) p var->next
$12 = (struct variable *) 0x0
Regards,
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-04-25 19:04:20 | Re: Vacuum-full very slow |
| Previous Message | Steve Crawford | 2007-04-25 18:51:28 | Re: Vacuum-full very slow |