[fpc-devel] I have created a openocd debugger-interface for lazarus, now some questions

[Michael Ring]

In the last days I have had a nice fight with lazarus-trunk, but it 
seems I succeeded in the end ;-)

I have integrated openocd debugger class as a child of the gdbmi 
debugger classes, basic code upload & debugging now works for me in 
lazarus, still has some rough edges, this is why I am seeking for 
support by the arm-embedded hackers here in fpc-devel.

Do you guys have some best practices, magic startup scripts, etc... that 
make debugging of embedded targets more successful? I would like to 
include those tricks in the debugger class.

single stepping works, I seem to have trouble with creating breakpoints, 
I run out of them very fast, for example lazarus shows me 3 breakpoints, 
openocd complains that it is already at breakpoint #11, is this a well 
known problem or do I need to investigate deeper into this?

Also, visibility of variables is not that good, I can see simple 
variables in my procedures but more complex variables are usually 
invisible. Is this a known problem or is there just some magic I need to 
apply in the startup of gdb?

Another issue is that I cannot do the loading of my binary from within 
gdb, at the moment I still need to do direct telnet communication with 
openocd.

Which library should I use for doing the telnet session? I read on the 
freepascal wiki  that fcl-net is a little outdated, so which library 
should I use, I do not want to introduce additional dependencies to the 
lazarus build by including synapse or indy.

Lots of questions, I know, but perhaps some of you guru's can help ;-)

btw, If someone whats to give the lazarus version a try, I have binaries 
for MacOS i386 and will have binaries for Windows i386 or Linux soon (in 
case anybody is interested) I still need to cleanup my changes, there 
are now way too much additional debug messages in the sourcecode of the 
gdbmi classes.

Michael