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

st-util segfaults when printing array in gdb #256

Closed
dflogeras opened this issue Aug 13, 2014 · 5 comments · Fixed by #394
Closed

st-util segfaults when printing array in gdb #256

dflogeras opened this issue Aug 13, 2014 · 5 comments · Fixed by #394

Comments

@dflogeras
Copy link
Contributor

I have a chunk of code that has a global array defined in main as:

static float output[ 2048 ];

When I attempt to print it's contents with either "print output" or even "print output @ 10" st-util crashes with the following messages:

GDB connected.
libusb_handle_events() timeout
[!] send_recv
libusb_submit_transfer(-6)
[!] send_recv
Segmentation fault

I've tried both the 1.0.0 release, and master (f12bde)

Printing normal variables seems to work fine.

I am using a STM32F4-DISCOVERY board, and ChibiOS, my toolchain was created with Gentoo's crossdev.

@xor-gate
Copy link
Member

xor-gate commented May 5, 2016

Please test again with latest tools in master, keep in mind the gdb-server stubs with the stlink tools are not as complete and tested as the stubs shipped with OpenOCD.

@dflogeras
Copy link
Contributor Author

Wow I forgot about this one, came up with a similar test and confirmed it is still broken on 1.0.0 and 1.1.0, then tried current master d252443 and the issue goes away. Thank you very much!

@xor-gate
Copy link
Member

xor-gate commented May 5, 2016

Great!, thanks for verifying.

@xor-gate
Copy link
Member

xor-gate commented May 5, 2016

FYI, I have bumped v1.2.0. Have fun!

@dflogeras
Copy link
Contributor Author

TYVM, was hoping for a new numbered release, now I'll see if I can make a Gentoo ebuild and get it in the official tree.

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

Successfully merging a pull request may close this issue.

3 participants