-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
05-led-roulette GDB problem. #495
Comments
My judgment is that your console gdb is not loaded into the device target. As stated in the book, you should select different devices according to the Is it convenient for you to send the shell command you entered? |
Hope I'm not assuming too much, but I may be able to help. Since I likely came across the same issue using the gdb command from the book, getting exactly the same output. Note that the section in the book is a bit unclear on which directory to switch to in the new shell:
I initially assumed the "project directory" would be the same directory I ran cargo-embed in, e.g. Fixing this is very simple:
If you still have issues, you can always just use the absolute path. Cargo embed will tell you where it places the file in the output with "Target: <path>". |
thanks @AlexanderRitter02 it worked!! |
Fixed in #520 |
When I am debugging as the book said and entered "target remote :1337" in the gdb mode, here is the outcome:
Remote debugging using :1337
warning: No executable has been specified and target does not support
determining executable automatically. Try using the "file" command.
0x00000100 in ?? ()
Have I done something wrong?
Waiting for answers.
Thanks.
The text was updated successfully, but these errors were encountered: