-
Notifications
You must be signed in to change notification settings - Fork 6
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
Shutdown crash with GLIP USB3 backend #32
Comments
Two things you can try:
|
Thanks for the reply!
|
Ah, now I see it. You're having a shutdown crash. In the GDB trace, you have "Demonstrator runner finished." and then the threads are exiting. That's confirmed by the Valgrind output, where we have
The shutdown process is a bit fragile especially with the USB GLIP backend, as libusb has slightly unexpected/unclean behavior around thread shutdown sometimes. I'll look into it later today. If you only want to avoid the crash, simply remove the |
Thanks for looking into that! |
STM loggers stream data at random times, so they expose the problem best. But it could equally happen with any other debug module which still sends data while the host side is in the process of being torn down. |
Python currently crashes after executing my script to connect to an FPGA, program the cores, and trace the software output. However, it only crashes when I use the stm loggers.
Here's the output when I execute the script with:
gdb -return-child-result -batch -ex r -ex bt --args ./venv/bin/python3 src/host/demonstrator_runner/demonstrator_runner.py
The text was updated successfully, but these errors were encountered: