• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 5757 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setting an entry point

Mark Griffiths
Note: This was originally posted on 23rd May 2013 at http://forums.arm.com

Hello,

Finally I managed to build a static library and I have a xyz.a file and some xyzs.o files.  The entry point is xyz_init and I put this as so in the debugger, however on loading I get this:

WARNING(CMD399-COR168):
! Failed to start the target
! No function named "xyz_init" could be found
WARNING(CMD407): Trying the entry point instead
ERROR(CMD426): Cannot find symbol to start or entrypoint, the file or load commands may be used to set the entrypoint

How can I make the debugger see my entry point?  Also, how do I load up some symbol files?

Thanks.
Parents
  • Arm Employee Badge
    Note: This was originally posted on 24th May 2013 at http://forums.arm.com


    How can I make the debugger see my entry point?  Also, how do I load up some symbol files?


    There are a few of things that could be preventing the debugger from seeing the xyz_init symbol:
    - you might not be loading the image's symbols
    [size=2]- the image might not have symbols in it: check the build commands and/or look at the image symbol table by opening it with the ELF Content Editor[/size]
    - the linker might have pulled in the code from the library that you think it did: produce a linker map/symbol file and/or use the ELF Content Editor

    It's strange that the debugger seems to think that your image has no entry point.  What is you link command?  What is the earlier output in the Commands view?

    You can load symbol files in at least three ways:
    - in the debug configuration, Files pane: check Load Symbols on the image you are downloading (if any) http://infocenter.ar...9980637970.html
    - in the same pane lower down:  add a Load Symbols from File entry
    - in the Commands view (or Debugger pane of the debug config): manually use an add-symbol-file (etc.) command
Reply
  • Arm Employee Badge
    Note: This was originally posted on 24th May 2013 at http://forums.arm.com


    How can I make the debugger see my entry point?  Also, how do I load up some symbol files?


    There are a few of things that could be preventing the debugger from seeing the xyz_init symbol:
    - you might not be loading the image's symbols
    [size=2]- the image might not have symbols in it: check the build commands and/or look at the image symbol table by opening it with the ELF Content Editor[/size]
    - the linker might have pulled in the code from the library that you think it did: produce a linker map/symbol file and/or use the ELF Content Editor

    It's strange that the debugger seems to think that your image has no entry point.  What is you link command?  What is the earlier output in the Commands view?

    You can load symbol files in at least three ways:
    - in the debug configuration, Files pane: check Load Symbols on the image you are downloading (if any) http://infocenter.ar...9980637970.html
    - in the same pane lower down:  add a Load Symbols from File entry
    - in the Commands view (or Debugger pane of the debug config): manually use an add-symbol-file (etc.) command
Children
No data