ESP32 Forum

Posted: **Wed Oct 29, 2025 4:11 am**

Hello,

I'm using the ESP-IDF extension in VS Code to debug an ESP32-S3 project.

When I set a breakpoint and try to "Step Into" a printf function call, VS Code shows an error: "The editor could not be opened because the file was not found."

Is this a bug, or is there a misconfiguration on my end? What do I need to do to allow the debugger to correctly navigate to the source code of standard library functions like printf?

Thanks for your help.

Posted: **Fri Oct 31, 2025 5:53 am**

launch.json：

Code: Select all

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "gdbtarget",
      "request": "attach",
      "name": "Eclipse CDT GDB Adapter"
    },
    {
      "type": "espidf",
      "name": "Launch",
      "request": "launch"
    }
  ]
}

Posted: **Fri Oct 31, 2025 6:17 am**

I seem to understand now...

The printf function is precompiled in ROM, and the source code is not available, so the file content cannot be displayed during debugging.

ESP32 Forum

[VS Code] Debugging: "File not found" when stepping into printf on ESP32-S3

[VS Code] Debugging: "File not found" when stepping into printf on ESP32-S3

Re: [VS Code] Debugging: "File not found" when stepping into printf on ESP32-S3

Re: [VS Code] Debugging: "File not found" when stepping into printf on ESP32-S3