![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am looking at a problem with an ABF application that is being ported to 9.2/9.3 x86 64-bit Linux. *There seems to be a problem with a couple of SELECT-loops which looks like the number of pre-fetched rows is somehow being messed up so that sometimes a bogus extra row is returned and other times too few rows are returned. I was thinking it'd be easy enough to trace it with gdb but the community builds don't seem to have been compiled with -g. *What is the least amount of work I'd need to do to build the ABF library with -g from source? |
#3
| |||
| |||
|
|
On Nov 9, 2:06*pm, Roy Hann <specia... (AT) processed (DOT) almost.meat> wrote: I am looking at a problem with an ABF application that is being ported to 9.2/9.3 x86 64-bit Linux. *There seems to be a problem with a couple of SELECT-loops which looks like the number of pre-fetched rows is somehow being messed up so that sometimes a bogus extra row is returned and other times too few rows are returned. I was thinking it'd be easy enough to trace it with gdb but the community builds don't seem to have been compiled with -g. *What is the least amount of work I'd need to do to build the ABF library with -g from source? Assuming you have a working build area, the following should build all of ABF in debug: cd $ING_SRC/front/abf jam -a -sII_OPTIM=-g You'll find the updated libraries in $ING_BUILD/lib. It might be possible to target a particular sub-section of the code for which you would cd to that directory and run: jam -a -sII_OPTIM=-g cd $ING_SRC/front/abf jam the second jam rebuilds the libraries with the parts you built in debug. |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Although you are looking for a way to debug this, you might like to know that bug 122422 results in these symptoms. In ABF nested select loops can terminate early or run over with junk being output - that junk obviously can then cause all sort of odd results. A patch containing a fix for this bug is likely to resolve your problem, without the need to use gdb. Fixed in patch 13599 for Ingres 9.2 on NPTL Linux on x86_64 available from ESD. Fix 500127 in main, which might be of use for 9.3 (don't know that). |
![]() |
| Thread Tools | |
| Display Modes | |
| |