Hi Guys, Andrew, yes, I have checked all the settings in the Debug Configuration settings and they all point to the correct files, and I have the correct file in my load command, but gdb is crashing even before it connects to openocd. I also cannot find the "verbose console mode" checkbox in the debugger tab in Debug configurations dialog, do you have a different version? I am running eclipse version: Version: Helios Release Build id: 20100617-1415 And openocd is Open On-Chip Debugger 0.5.0-dev version ..
Øyvind, the command line doesn't crash .... so not sure what eclipse/gdb is doing. It seems my executable is the problem, because when I replace the "good" project elf file with the "bad" project elf, the good project fails as well ... To duplicate the project, I just did a copy/paste within the eclipse IDE and everything built ok .... really confused why this object file crashes the debugger .. Cheers, Bernie On Mon, Feb 14, 2011 at 5:00 PM, Andrew Leech <[email protected]>wrote: > On Mon, Feb 14, 2011 at 12:48 PM, Bernard Mentink <[email protected]> > wrote: > > Hi All, > > I apologize for posting a somewhat openocd off-topic question, but I am > in a > > bind. > > I have been using openocd and gdb from within eclipse quite happily, > until I > > duplicated a project to start a new one, and tried debugging it. > > When gdb launches from within eclipse, I get a windoze crash dialog box, > > then the following error: > > "Error in final launch sequence > > Connection is shut down" > > However if I launch gdb from the old project it is fine. The debug > settings > > between projects are identical .... apart from the object code .. > > If I copy the "good" object code into the new project location ... I > still > > get the error, so doesn't look like the object code is the issue .. > > Anyone offer any suggestions? > > The only thing that comes to mind is checking to be sure that the > debug configuration settings are all referencing the new files in the > new project. On the main tab of debug configurations ensure the new > project is selected, and that the c/c++ application is set to the new > object file. Then on the startup tab that the image and symbols are > either set manually to the new one or to project binary (which has > just been checked). > > And/or, if your object file is loaded with openocd (I load mine > through gdb) check that your openocd script is pointing to the new > object/bin file. > > > I don't know how to get more info from gdb as to what is going on .. > > Depends on whether the problem is arising from gdb or openocd. openocd > script can be changed to add --debug <0-3> to its command line. > For GDP I've got a "verbose console mode" checkbox on the Debugger tab > of debug configurations (just under the popup of protocol version) > that when enabled gives a heap of extra console output. > > For reference I'm using Eclipse helios sr1 with GDB Hardware > Debugging, yagarto for gcc/gdb and git trunk openocd. > > I know what you mean about this being somewhat off topic, but I feel > your pain, there doesn't seem to be a particularly good place to > discuss issues relating to the overall open source toolchain setup. > Similarly I've got serious issues getting pipe openocd working > properly in helios. It'd be great to have running, but in the rare > configurations it actually connects to the target correctly, it debugs > (ie step, read regs, etc) at such an abysmally slow pace it's > unusable, whereas the traditional method of external tool openocd and > sockets works fine. This in on windows too, so it's quite possibly > just that pipes on windows are a bit of a hack? Either way I've given > up on pipe for now. > > Andrew > -- You always have believers and scepticts.. A True inventor is always a believer..
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
