Bill Thoen <[EMAIL PROTECTED]> writes:
> I'm a bit out of my depth with using these debugging tools and
> interpreting their results, but I think the problem is due to the output
> being just too big for interactive display.
Well, I can certainly believe it's related to the amount of data
involv
I'm a bit out of my depth with using these debugging tools and
interpreting their results, but I think the problem is due to the output
being just too big for interactive display. Using the same query with
tighter limits in the WHERE clause works perfectly. When I changed the
SQL script to writ
Bill Thoen <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 0x003054264571 in fputc () from /lib64/libc.so.6
> #1 0x0040dbc2 in print_aligned_text (title=0x0, headers=0x5665d0,
> cells=0x2f8fc010, footers=0x557c90,
> opt_align=0x557ef0 'l' , "rr", 'l' times>, "rl lll", opt
