• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 2274 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

DS-5 debugger errors on beagleboard

kaijunI tried tang

I try to debug hello example on beagleboard with DS-5, I got errors as follows,

Connected to gdbserver at
file "/home/tang/Project/hello/stripped/hello"
WARNING(IMG53): No line debug information in the image hello
WARNING(LUX47): The image /home/tang/Project/hello/stripped/hello does not match the target
ERROR(LUX48-TAD10-NAL79):
! Failed to set up shared library support
! Failed to read 4 bytes from address 0x0001059C
! Remote GDB returned error code 0x01
add-symbol-file "/home/tang/Project/hello/hello" 0x0
set start-at main
start
Starting target with image /home/tang/Project/hello/stripped/hello
ERROR(TAD8-NAL79):
! Unable to run device 1
! Failed to enable software breakpoints. Remote GDB returned error code 0x01
quit
Successfully disconnected from stopped target gdbserver

But if I copy stripped hello to begaleboard, then run it. It works.

Parents
  • 0 Arm Employee Badge

    The warnings suggest that there are two problems.

    The first "No line debug information" when issuing the "file" command probably means that you are trying to load debug information from an image that has been stripped. The argument to the "file" command should normally be an unstripped image.

    The second warning "The image ... does not match the target" means that the debugger thinks that the argument to the "file" command represents a different image from the one that is running on the beagleboard. The debugger compares the two images by looking at a number of code instructions at various places in the image and seeing whether they match. The comparison does not include debug information, and so it should not matter whether one of the images is stripped or not. Check that the images really are from the exact same build, and only differ in whether they have been stripped or not. If you want to be absolutely sure of this, use the same unstripped image in both the debugger and on the board.

Reply
  • 0 Arm Employee Badge

    The warnings suggest that there are two problems.

    The first "No line debug information" when issuing the "file" command probably means that you are trying to load debug information from an image that has been stripped. The argument to the "file" command should normally be an unstripped image.

    The second warning "The image ... does not match the target" means that the debugger thinks that the argument to the "file" command represents a different image from the one that is running on the beagleboard. The debugger compares the two images by looking at a number of code instructions at various places in the image and seeing whether they match. The comparison does not include debug information, and so it should not matter whether one of the images is stripped or not. Check that the images really are from the exact same build, and only differ in whether they have been stripped or not. If you want to be absolutely sure of this, use the same unstripped image in both the debugger and on the board.

Children