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.

Debug mode not starting in SAM Local

See original GitHub issue

Tried starting “-d” mode using invoke and start-api. Both will not listen in debug mode.

Status: Image is up to date for lambci/lambda:go1.x

Mounting dscemails (go1.x) at http://127.0.0.1:3000/collect [POST]

You can now browse to the above endpoints to invoke your functions.
You do not need to restart/reload SAM CLI while working on your functions,
changes will be reflected instantly/automatically. You only need to restart
SAM CLI if you update your AWS SAM template.

Even after sending data, VS Code Debugger still can’t connect to any port I set.

Debugging with legacy protocol because Node.js version could not be determined (Error: connect ECONNREFUSED 127.0.0.1:5858)

Issue Analytics

State:
Created 5 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

8reactions

sanathkrcommented, Jun 1, 2018

Starting SAM CLI in debug mode is not sufficient to attach a debugger. You should send a invoke request first to spin up the Docker container, which will make the port available for debugger to attach:

Start SAM CLI start-api with --debug-port flag
Send a HTTP request to the endpoint to invoke the Lambda function. At this point, the Docker container is started and your runtime process is waiting for debugger to attach
Attach debugger thru IDE. this should work.

Feel free to re-open the issue if the above didn’t work.

2reactions

fkmarecommented, Jun 20, 2018

Hi Is it possible to debug SAM Local with compiled languages, such as .NET Core?