Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • scilab scilab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 2,562
    • Issues 2,562
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 47
    • Merge requests 47
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • scilabscilab
  • scilabscilab
  • Issues
  • #1086
Closed
Open
Issue created Nov 20, 2004 by scilab bot@scilabbot💬Owner

ScilabEval "resume(0)" "sync" fails In a paused environment, ScilabEval "resu

Reported by François VOGEL

-- Bug description --


ScilabEval "resume(0)" "sync" fails

In a paused environment, ScilabEval "resume(0)" "sync" 
fails to resume execution.

ScilabEval "resume(0)" "seq" works OK for that purpose.

Testcase and steps to reproduce the bug are provided in the 
attachment below.

This attachment also contains my analysis of the causes of 
this wrong behavior. Fixing the bug should be limited to 
take the pause context into account in C2F(syncexec) in 
routines/system/parse.c instead of always setting Rstk[Pt]
=1001 in that function (line 1501).

Francois


-- Scilab error message --





-- How to reproduce the bug --
Assignee
Assign to
Time tracking