Open
Description
Describe the bug
Attempting to debug with the ThreadLib debug library - get message GDB debugger terminated unexpectedly.
To Reproduce
Steps to reproduce the behavior:
- At the top of your code:
#include <ThreadDebug.h> // UartDebugCommInterface debugComm(SERIAL1_TX, SERIAL1_RX, 230400); // ThreadDebug threadDebug(&debugComm, DEBUG_BREAK_IN_SETUP); UsbDebugCommInterface debugComm(&SerialUSB); ThreadDebug threadDebug(&debugComm, DEBUG_NO_BREAK_IN_SETUP);
- Build & Download
- Start debug session by Debug->Start Debugging
- See error - GDB debugger terminated unexpectedly.
Expected behavior
Debug session should start.
Screenshots
If applicable, add screenshots to help explain your problem.
Message pops up and goes away.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Version [e.g. 22]
Windows 10 - 2020 latest released from M$
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
jwestmoreland commentedon Aug 24, 2020
From the command line - using what was compiled by the 0.1.0 IDE - it does run:
ubidefeo commentedon Aug 25, 2020
hi John
I'm glad you downloaded this right away.
@kittaakos is looking into this, we must have added some regression in the communication between UI and CLI.
As I was telling you a couple days back the debugger didn't get much love this time around, as we had to focus on releasing a more stable editor with broader compatibility, but it's definitely on our list for the next few weeks.
At least now you have access to nightly builds, so if it's something we figure out quickly you'll be able to get a working version faster than 4 months from now :D
I'll make sure this issue gets updated as we know more.
Thank you :)
jwestmoreland commentedon Aug 25, 2020
Hello @ubidefeo ,
Yes, not much love appears to be no love at all actually; ;) - hope this can move forward but there's more ways to debug as we've discussed as well.
That's cool we have access to nightly builds now - thanks for letting us know about that!
And, thanks for looking at the debugger issues as well.
You are more than welcome!
Best Regards,
John W.
kittaakos commentedon Aug 25, 2020
I have a quick update: we have identified the breaking change. I built a CLI with a tiny modification locally, dropped it into the IDE and the debugger works.
jwestmoreland commentedon Aug 25, 2020
Hello @kittaakos ,
So, will this be in the nightly update or how can I give it a try?
Thanks,
John W.
kittaakos commentedon Aug 25, 2020
Yes, once we fix the issue and very it, we will make it available in the nightly.
I will keep you posted. Thank you for logging the bug.
jwestmoreland commentedon Aug 25, 2020
Hello @kittaakos ,
Thanks for getting to this so quickly!
And, sure, NP - been waiting for the ThreadLib stuff to get stable.
Thanks Again,
John W.
ubidefeo commentedon Aug 26, 2020
@jwestmoreland
you could try the nightly but we're also doing a patch release possibly today
kittaakos commentedon Aug 26, 2020
Please note, the nightly won't work until we have another CLI release.
kittaakos commentedon Aug 26, 2020
@jwestmoreland, we have a new IDE release with the debugger fix: https://github.com/arduino/arduino-pro-ide/releases/tag/0.1.1
jwestmoreland commentedon Aug 27, 2020
Hello @kittaakos ,
OK - thanks for that - and loaded it - just wondering, has anyone debugged anything with it?
I got this when I tried to debug:
From what I can tell, status (somewhat) unchanged from here.
Thanks,
John W.
kittaakos commentedon Aug 27, 2020
Of course.
On Windows and macOS, we verified the basic debugging features on a compiled sketch,
int
),On both Windows and macOS, we used an Arduino Zero board, plus we tried it with CMSIS-DAP debugger on Windows.
I do not know if debugging works with the Portenta board. @ubidefeo, can you please help with this?
jwestmoreland commentedon Aug 27, 2020
Hello @kittaakos ,
Thanks for the response.
Since this is the arduino-pro-ide 'forum' - thought Portenta as the target was/is implied.
Thanks,
John W.
pnaybour commentedon Aug 27, 2020
@jwestmoreland i am not to sure about the support for Portenta board.
8 remaining items
jwestmoreland commentedon Feb 24, 2021
@kittaakos ,
Can you let me know what's unclear now - I'm wondering what the actual question(s) is/are that you want me to answer?
Thanks,
John W.
ubidefeo commentedon Feb 26, 2021
hi @jwestmoreland
This is a fairly old thread.
We have since assessed that changes are to be made to the
arduino:mbed
core in order to get the ThreadDebug port to be recognised and used at the start of a debug session.The issue will remain open until we have this implemented and working :)
[-]v0.1.0 - Using TheadDebug Lib: GDB Debugger Terminated Unexpectedly.[/-][+]Using TheadDebug Lib: GDB Debugger Terminated Unexpectedly.[/+][-]Using TheadDebug Lib: GDB Debugger Terminated Unexpectedly.[/-][+]Using ThreadDebug Lib: GDB Debugger Terminated Unexpectedly.[/+]