Cant enable and find core dumped

Open
#880 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, python

Research direction

Start by reproducing the Python crash in the Docker container and investigate why ulimit -c unlimited does not produce a core dump or backtrace. Compare the container's behavior with the expected core-dump configuration and document a reproducible path to obtain the stack trace; done when the failure can be diagnosed from the generated output.

Written by the indexing model from the issue text.

Description

When my Python program fails in a Docker container, no core dump or backtrace is generated. I tried enabling it using ulimit -c unlimited, but it didn't help. I cannot find a stack trace to determine why my program is crashing. All I get is a corrupted size vs. prev_size message.

Dominant language
Dockerfile
Stars
2.8k
Forks
1.1k
Avg merge
3d 1h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker-library/python

All issues in docker-library/python

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.