Skip to content
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

[Chapter 5.3] Continue hangs, stuck at "0x00000000 in __vector_table ()" #564

Open
garrelj1 opened this issue Apr 15, 2024 · 4 comments
Open

Comments

@garrelj1
Copy link

garrelj1 commented Apr 15, 2024

Running on Kali Linux

I'm able to build and flash the code. Once I try to debug, I get the following:

(gdb) target remote :1337
Remote debugging using :1337
warning: while parsing target description (at line 4): Target description specified unknown architecture "armv7"
warning: Could not load XML target description; ignoring
0x00000000 in __vector_table ()

Notice 0x00000000 in __vector_table ()

After adding a break point, and continuing, it just hangs:

(gdb) b main
Breakpoint 1 at 0x15c: file src/05-led-roulette/src/main.rs, line 9.
Note: automatically using hardware breakpoints for read-only addresses.

(gdb) continue
Continuing.

I've also tried step, which gives

(gdb) step
Single stepping until exit from function __vector_table,
which has no line number information.

Program received signal SIGINT, Interrupt.
0x00000000 in __vector_table ()

And I've tried stepi, which gives

(gdb) stepi

Program received signal SIGINT, Interrupt.
0x00000000 in __vector_table ()

Any ideas of how else to debug or get further?

@BartMassey
Copy link
Member

Could you please take a look at https://docs.rust-embedded.org/discovery-mb2 and https://github.com/rust-embedded/discovery-mb2 and see if you can reproduce this issue there? If so, please file an issue there and we'll try to get it figured out and fixed.

@Michal2404
Copy link

Have you tried running gdb-multiarch instead of gdb? I had the same issue and it helped me.

@zanebliss
Copy link

@Michal2404 What did you do exactly to fix this? Did you use gbd-multiarch as the command to run instead of gdb?

@Michal2404
Copy link

Exactly. It depends on which version of gdb you have installed (chapter 3 of the book).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants