>
>
> I'm running:
> Version: Helios Service Release 1
> Build id: 20100917-0705
>
> I highly suggest you update it, when I first tried the original Helios
> it was so incredibly buggy I switched back to the previous release
> until this update came out.
>
I have just updated it and re-installed cdt-master from the zip file .... no
change, still the problem.
> Also, are you using the GDB hardware debugging module to talk to
> openocd (part of CDT) with it? (aka not something else like older
> zylin... don't know if it's even possible with helios)
> I'm using it in standard GDB Hardware Debugging Launcher mode (down
> the bottom of the Debug Configurations window), not in DSF mode (I
> assume you'll only get this choice if you've installed DSF stuff from
> CDT as well). The verbose checkbox may have come with SR1, or with
> this mode, I'm not entirely sure. Chances are it's a SR1 thing though.
>
I am using GDB hardware dubugging and using DSF (although the problem is
with standard and DSF)
I found that the verbose checkbox is only on the standard debugger, the
output from that is:
1-gdb-set confirm off
1^done
(gdb)
2-gdb-set width 0
2^done
(gdb)
3-gdb-set height 0
3^done
(gdb)
4-interpreter-exec console echo
4^done
(gdb)
5-gdb-show prompt
5^done,value="(gdb) "
(gdb)
6-gdb-set new-console on
6^error,msg="No symbol table is loaded. Use the \"file\" command."
(gdb)
7 symbol-file C:\\eclipse\\TEST\\dbg\\Trial.elf
&"symbol-file C:\\\\eclipse\\\\TEST\\\\dbg\\\\Trial.elf\n"
symbol-file C:\\eclipse\\TEST\\dbg\\Trial.elf
8-gdb-exit
I don't know why it is complaining about the symbol file .. doesn't it use
the .elf file? Any idea's?
> > Ø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 ..
>
> With copying projects, I've done this a number of times myself - often
> I forget to change the build directory in the project settings, and
> while it looks like it's compiling fine, it's actually compiling the
> old project still because it's pointing to that folder.
> These days in the Project settings -> C/C++ Build -> Builder settings
> I set the Build Directory to ${ProjDirPath} which removes this
> problem. This is for a makefile based system, which I assume you're
> using.
>
> Andrew
>
Yep, I had checked and re-checked that .. it is definetely compiling the new
code ..
Many Thanks,
Bernie
--
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
