Macaulay2 / Macaulay2/M2

Crash in parallel gb computations

Open
#4,226 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Engine threads
Dominant language
Macaulay2
Stars
435
Forks
297
Avg merge
4d 20h
Merged PRs (30d)
11

Description

Another consistent crash that I can't extract in a simple example:
```m2
3# GBRing::gbvector_cancel_lead_terms(FreeModule const*, FreeModule const*, gbvector const*, gbvector const*,
gbvector const*, gbvector const*, gbvector*&, gbvector*&) at /home/mahrud/M2/M2/Macaulay2/e/gbring.cpp:1074
4# gbA::compute_s_pair(gbA::spair*) at /home/mahrud/M2/M2/Macaulay2/e/gb-default.cpp:1331
5# gbA::reduce_kk(gbA::spair*) at /home/mahrud/M2/M2/Macaulay2/e/gb-default.cpp:1364
6# gbA::reduceit(gbA::spair*) at /home/mahrud/M2/M2/Macaulay2/e/gb-default.cpp:1585
7# gbA::do_computation() at /home/mahrud/M2/M2/Macaulay2/e/gb-default.cpp:2528
8# gbA::start_computation() at /home/mahrud/M2/M2/Macaulay2/e/gb-default.cpp:2601
9# Computation::status() const at /home/mahrud/M2/M2/Macaulay2/e/comp.hpp:49
10# rawStartComputation at /home/mahrud/M2/M2/Macaulay2/e/interface/groebner.cpp:272
```

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.

Research direction

Start at e/gbring.cpp:1074, then follow the reported call chain through e/gb-default.cpp and e/interface/groebner.cpp. Reproduce the crash in a parallel Gröbner-basis computation and identify a triggering case; done means the computation no longer crashes for that case and the relevant regression is covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.