question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug Report]: Build crashing on custom OpenOCD build (VSC-532)

See original GitHub issue

Pre Bug Report Checklist Before reporting any bug please make sure of these points.

  • Make sure you have searched for existing bugs and features request before you post an issue.
  • This is a bug report for the ESP-IDF Visual Studio Code extension and not an ESP-IDF bug report.
  • I’ve read the docs and found no information that could have helped solving the issue.

Describe the bug

I’m having similar symptoms as https://github.com/espressif/vscode-esp-idf-extension/issues/270, but my case is slightly different, I’ll be thorough on this bug report…

After enabling remote_bitbang on OpenOCD (see PR https://github.com/espressif/openocd-esp32/pull/134), I cannot seem to be able to do anything with the extension anymore since the following error appears on any action (i.e Build):

{
  "message": "Open On-Chip Debugger  v0.10.0-esp32-20201202-2-g7e342cad (2021-01-02-23:47)\nLicensed under GNU GPL v2\nFor bug reports, read\n\thttp://openocd.org/doc/doxygen/bugs.html\n",
  "stack": "Error: Open On-Chip Debugger  v0.10.0-esp32-20201202-2-g7e342cad (2021-01-02-23:47)\nLicensed under GNU GPL v2\nFor bug reports, read\n\thttp://openocd.org/doc/doxygen/bugs.html\n\n    at /Users/romanvg/.vscode-insiders/extensions/espressif.esp-idf-extension-0.6.0/dist/extension.js:1:7720\n    at ChildProcess.exithandler (child_process.js:303:7)\n    at ChildProcess.emit (events.js:315:20)\n    at ChildProcess.EventEmitter.emit (domain.js:483:12)\n    at maybeClose (internal/child_process.js:1021:16)\n    at Socket.<anonymous> (internal/child_process.js:443:11)\n    at Socket.emit (events.js:315:20)\n    at Socket.EventEmitter.emit (domain.js:483:12)\n    at Pipe.<anonymous> (net.js:674:12)",
  "level": "error",
  "timestamp": "2021-01-06T11:34:05.666Z"
}

The error log above occurs as well if having OpenOCD up and running… my best guess is that idf_tools.py version checking logic is interfering with the extension Build task/command?

To Reproduce

Install a slightly tweaked OpenOCD version (different than the one shipped with the extension).

Expected behavior

Everything working fine as it should? 😃

Screenshots On each Build task, the following error block appears in the extension’s error log:

Skärmavbild 2021-01-06 kl  22 55 01

Environment (please complete the following information):

  • OS Name & Version: MacOS X 10.15.2 (Catalina)
  • VSCode Version: Insiders, latest
  • ESP-IDF Version: master
  • Python Version: 3.9.1

Logs

As shown above in the description.

Additional context

Please see PR https://github.com/espressif/openocd-esp32/pull/134 for more context. Also providing env vars I’m using:

  "idf.espIdfPath": "/Users/romanvg/dev/esp-idf",
  "idf.openOcdConfigs": [
    "interface/remote_bitbang.cfg",
    "target/esp32s2.cfg"
  ],
  "idf.customExtraVars": "{\"OPENOCD_SCRIPTS\":\"/Users/romanvg/.espressif/tools/openocd-esp32/v0.10.0-esp32-20201202/openocd-esp32/share/openocd/scripts\"}",

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10

github_iconTop GitHub Comments

2reactions
gost-serbcommented, Jan 8, 2021

@brainstorm

EDIT: yarn debugPreTask to switch into development mode…

Looks like the extension was moved to yarn some time ago but some pieces of code still working with npm though. I would recommend you instead of commenting out "preLaunchTask": "npm: debugPreTask", line in launch.json try to replace it with "preLaunchTask": "yarn: debugPreTask",

Regarding the issue itself: did you check OpenOCD output on the output tab (Ctrl+Shift+U) when this issue occurs? image

1reaction
brianignacio5commented, Jan 8, 2021

There is a OpenOCD output tab (next to terminal) which is the openocd server log. The log you shown in the issue description is just printing openOCD version as an error, not related to the issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Bug Reporting - OpenOCD
If OpenOCD is crashing, there are two very effective things you can do to improve your chances of getting help on the development...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found