ERROR while running Cbc. Signal SIGSEGV caught.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- debian, linux, python
- Domain
- backend, operating-systems
Research direction
Start by reproducing the crash on amd64 with Debian bookworm or trixie, Python 3.11 or 3.13, and Python-MIP 1.16rc0, using the reported cbc-c-linux-x86-64.so stack trace as the entry point. Compare the same workload on ARM and Ubuntu, and capture the missing reproduction files and full failing call so the issue is reduced to a repeatable case without SIGSEGV.
Written by the indexing model from the issue text.
Description
Describe the bug
Got SIGSEGV error on amd64 machines
To Reproduce
Steps to reproduce the behavior please include attached any files needed to reproduce the error. We can only help you if we can reproduce the error ourselves and debug.
Expected behavior
No error
Desktop (please complete the following information):
- Operating System, version:debian trixie (also on bookworm)
- Python version: 3.11, also 3.13
- Python-MIP version (we recommend you to test with the latest version): 1.16rc0
Additional context
Getting stack trace.
/root/dao/venv/day_ahead/lib/python3.13/site-packages/mip/libraries/cbc-c-linux-x86-64.so(_Z15CbcCrashHandleri+0x119) [0x7efdc6dc3459]
/lib/x86_64-linux-gnu/libc.so.6(+0x3fdf0) [0x7efdd1cecdf0]
python3(_PyObject_MakeTpCall+0x1dd) [0x5471cd]
python3(_PyEval_EvalFrameDefault+0x2661) [0x563da1]
python3(PyEval_EvalCode+0xcc) [0x55d48c]
python3() [0x6ab8d1]
python3() [0x6a899c]
python3() [0x6b9943]
python3() [0x6b93e3]
python3() [0x6b921e]
python3(Py_RunMain+0x3c1) [0x6b86f1]
python3(Py_BytesMain+0x2b) [0x6838eb]
/lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7efdd1cd6ca8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7efdd1cd6d65]
python3(_start+0x21) [0x682c81]
Only errors on amd64 machines.
Works well on arm-machines
With Debian GLIBC 2.36-9+deb12u13) 2.36 it goes wrong
With Ubuntu GLIBC 2.41-6ubuntu1.1) 2.41 there are no problems.
- Dominant language
- Linear Programming
- Stars
- 601
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coin-or/python-mip
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
coin-or/python-mip#426 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
coin-or/python-mip#425 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
coin-or/python-mip#423 · 4 comments · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
coin-or/python-mip#422 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
coin-or/python-mip#420 · 4 comments ·
All issues in coin-or/python-mip
Similar issues
-
schema_dict_to_pydantic_model TypeError on JSON Schema type arrays → extract falls back to free-text Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
browser-use/browser-use#5904 ·
-
type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ynput/ayon-python-api#363 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug severity:low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100