On Mon, 18 May 2009, Øyvind Harboe wrote:
$ gdb ../openocd --args openocd
... ends up running /usr/bin/openocd ...
Try
gdb --args openocd -f interface/xxx.cfg -f target/xxxx.cfg ...
This runs the one (r1409) in /usr/bin, not my newly compiled one.
If I find the actual executable, which I think is in src/.libs/openocd,
and try to tell gdb to run that, I get:
$ gdb ../.libs/openocd
(gdb) set args -f ../../../openocd-usr8200-jlink.cfg
(gdb) run
Starting program: <path>/src/.libs/openocd -f ../../../openocd-usr8200-jlink.cfg
<path>/src/.libs/openocd: error while loading shared libraries:
libopenocd.so.0: cannot open shared object file: No such file or directory
Program exited with code 0177.
(gdb)
Any attempt to pass --args openocd results in the installed
/usr/bin/openocd being run in the debugger, and not my compiled version.
=> The move to "libify" openocd has broken some use-cases
I wasn't going to get embroiled in the development discussions, because
active work is good for open source projects, but I wish the breaking
work had been done in a branch so that others could carry on. My (limited)
contributions have been delayed by spending time just getting my
environment working again._______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
