arduino / arduino/ArduinoCore-mbed

New ThreadDebug Commit - g++ not found in %PATH%

Open
#46 20 comments 0 reactions 0 assignees View on GitHub
waiting for feedback
Dominant language
C
Stars
411
Forks
225
PR merge metrics
No merged PRs in 30d

Description

Hello All (Martino),

Trying your [latest commit](https://github.com/arduino/ArduinoCore-mbed/commit/197b1b8a194ce9435cf7faed53f447cfa0e6458d) with the ThreadDebug lib - getting this:

![new-threadlib-commit](https://user-images.githubusercontent.com/2308903/91516886-6f207c00-e8a1-11ea-8342-5e7ae1139088.jpg)

Compilation error: Error: 2 UNKNOWN: exec: "g++": executable file not find in %PATH%.

Probably an easy one to fix - just wanted to report it - I'll see if I can do a workaround since I really want to see this run.

Compiling...
{
"sketchUri": "file:///c%3A/tmp/demo-web-server/demo-web-server.ino",
"fqbn": "arduinobeta:mbed:envie_m7_thread_debug", <=== is that a possible reason?
"optimizeForDebug": true
}

Also seeing:
Error during Debug: Cannot get command line for tool: cannot get programmer tool: undefined 'debug.tool' property

It does appear to be running from the command line:
C:\tmp\demo-web-server\build\arduinobeta.mbed.envie_m7>C:\Users\John\AppData\Local\Arduino15\packages\arduino\tools\arm-none-eabi-gcc\7-2017q4\bin\arm-none-eabi-gdb -ex "set pagination off" --baud 230400 -ex "set target-charset ASCII" -ex "set print pretty on" -ex "set remotelogfile mri.log" -ex "target remote COM4" demo-web-server.ino.elf
GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from demo-web-server.ino.elf...done.
Remote debugging using COM4
setup () at c:\tmp\demo-web-server/demo-web-server.ino:28
28 void setup() {
(gdb) finish
Run till exit from #0 setup () at c:\tmp\demo-web-server/demo-web-server.ino:28
Note: automatically using hardware breakpoints for read-only addresses.
[New Thread 604075640]
[New Thread 604081468]
main () at C:\Users\john\AppData\Local\Arduino15\packages\arduinobeta\hardware\mbed\1.2.2\cores\arduino\main.cpp:47
47 loop();

Also - in ThreadDebug 'mode' - two identical COM ports are listed:

![two-portenta-com-ports-thread-debug-mode](https://user-images.githubusercontent.com/2308903/91526768-3ab8ba00-e8b9-11ea-8b85-abdedb4dcda1.jpg)

Thanks!
John W.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the referenced ThreadDebug commit and the Windows compilation and debug-launch path for fqbn arduinobeta:mbed:envie_m7_thread_debug. Reproduce the missing g++ error, undefined debug.tool error, and duplicate COM-port entries; done means each reported ThreadDebug symptom has a verified resolution or a documented cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.