Skip to content

fix: reduce MAXTFS/MAXMIRS from 1500 to 1000 to fix SIGABRT (exit 134)#54

Closed
marouenbg wants to merge 1 commit intonetZoo:develfrom
marouenbg:fix/puma-maxtfs-segfault
Closed

fix: reduce MAXTFS/MAXMIRS from 1500 to 1000 to fix SIGABRT (exit 134)#54
marouenbg wants to merge 1 commit intonetZoo:develfrom
marouenbg:fix/puma-maxtfs-segfault

Conversation

@marouenbg
Copy link
Contributor

Problem

CI fails on both ubuntu-latest and macos-latest with exit code 134 (SIGABRT) when running PUMA.

Root cause: PUMA REGULATION struct array with MAXTFS=1500 creates a ~2 GB __DATA segment that exceeds the macOS Mach-O segment size limit. This causes dyld to fail loading shared libraries (libc++.1.dylib, libSystem.B.dylib), aborting the process before main() even runs.

Fix

Reduce MAXTFS and MAXMIRS from 1500 back to 1000 (matching PANDA). This brings the __DATA segment from ~2.0 GB to ~1.83 GB, within limits.

Verification

  • PUMA builds and runs successfully on macOS (arm64)
  • Output is byte-identical to the reference ToyOutput_FinalNetwork.pairs
  • All 4 PUMA tests pass (format, nonzero edges, miRNA check, network comparison)
  • All 3 PANDA tests continue to pass

Fixes https://github.com/netZoo/netZooC/actions/runs/22497581186

…Linux

PUMA's REGULATION struct array with MAXTFS=1500 creates a ~2GB __DATA segment
that exceeds the macOS Mach-O segment size limit, causing dyld to fail loading
libc++.1.dylib/libSystem.B.dylib with exit code 134 (SIGABRT).

Reducing MAXTFS and MAXMIRS to 1000 (matching PANDA) brings __DATA under the
limit. Output is verified identical with the toy dataset reference.
@marouenbg marouenbg force-pushed the fix/puma-maxtfs-segfault branch from 43a25c1 to 935b92d Compare February 27, 2026 18:39
@marouenbg marouenbg closed this Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant