Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 403
    • Issues 403
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2528
Closed
Open
Created Jan 27, 2026 by Jordy Aaldering@JordyAalderingDeveloper

Don't print file/location information in stack trace for interactive environments

See !599 (closed)

/**
 * Within interactive environments, such as a Jupyter notebook, file name
 * and line numbers do not correspond to the notebook file (but instead to
 * the generated file). Such files are always in the tmp directory. If this
 * is the case, make sure we do not print nonsentical location information.
 */

Example:

*** Stack trace:
[0] main() at //tmp/jup-sackhmh76_s/tmp9674byxm.sac:65:1
 ╰⟶ main tried to call myTake2<[1],[1]>([ 3 ], [ 1 ]) at //tmp/jup-sackhmh76_s/tmp9674byxm.sac:67:19 but the predicates of myTake2 did not hold.
[SaC kernel] Executable exited with code 1

Should be:

*** Stack trace:
[0] main()
 ╰⟶ main tried to call myTake2<[1],[1]>([ 3 ], [ 1 ]) but the predicates of myTake2 did not hold.
[SaC kernel] Executable exited with code 1
Edited Jan 27, 2026 by Jordy Aaldering
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking