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

[STM32L4R5ZI]: gdb-multiarch uses wrong osabi #1386

Closed
6 tasks done
bauen1 opened this issue Apr 16, 2024 · 0 comments · Fixed by #1387
Closed
6 tasks done

[STM32L4R5ZI]: gdb-multiarch uses wrong osabi #1386

bauen1 opened this issue Apr 16, 2024 · 0 comments · Fixed by #1387

Comments

@bauen1
Copy link
Contributor

bauen1 commented Apr 16, 2024

  • I made serious effort to avoid creating duplicate or nearly similar issue

In order to allow developers to isolate and target your respective issue, please take some time to select the check boxes below and fill out each of the following items appropriate to your specific problem.

  • Programmer/board type: Unsure/STM32L4R5ZI Nucleo
  • Operating system an version: Linux
  • stlink tools version and/or git commit hash: v1.8.0
  • stlink commandline tool name: st-util
  • Target chip (and board, if applicable): Unsure

Further we kindly ask you to describe the detected problem as detailed as possible and to add debug output if available, by using the following template:

Commandline output:

(gdb) target extended-remote localhost:4242
Remote debugging using localhost:4242
[[REDACTED]]
(gdb) show osabi 
The current OS ABI is "auto" (currently "GNU/Linux").
The default OS ABI is "GNU/Linux".

Expected/description:

I would expect gdb to detect the osabi and set it e.g. to none, this is seemingly important, so that single stepping works, otherwise when stepping displacements will use ARM instructions instead of Thumb instructions, causing hard faults when stepping into the SRAM memory.

I am not sure, but by setting the osabi in the xml st-util provides to gdb, this should be set automatically.
I'll try and test that tomorrow and make a MR, should only take an hour or so.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.