Mark Wong wrote:
On 4/25/07, Michael Meskes <[EMAIL PROTECTED]> 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 ?? ()




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?

cheers

andrew


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to