Btw, Dave Fournier recommends that if you get an error message like the one below,
it is best to set a gdb breakpoint instead of stepping through the program line by line.
Incompatible bounds in dvar_vector& dvar_vector::operator = (const dvar_vector& t)
Below is the command to set a breakpoint in gdb.
(gdb) break ad_boundf
ad_boundf is a function that gets called right before the program exits. In fact, it calls the exit function.
Then you run,
If the program does stop at the ad_boundf function, you can print out the function call stack using the
The call stack history will give you clues to find the line of code that is causing the incompatible bounds
For simplicity, you could put the command break ad_boundf into the users home directory .gdbinit file. This
will automatically set the breakpoints and other commands. In the admb/utilities directory is a .gdbinit file
written by Chris Grandin from DFO that you can use.
Thanks Dave for pointing out a simpler way.
Let me know if you have other questions,