Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 336
    • Issues 336
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1645

Closed
Open
Created Oct 29, 2004 by Stephan Herhut@sahGuest

optIVE uses memory that never has been allocated!

Bugzilla Link 78
Created on Oct 29, 2004 10:40
Resolution LATER
Resolved on Nov 10, 2004 12:41
Version 1.00alpha
OS Solaris
Architecture Sun
Attachments minimod.sac

Extended Description

When compiling the attached sample module with
sac2c -noAP -noTSI -maxspec 0 -fun2lac 8 minmod.sac
optIVE accesses a non allocated memory region in function
CutVinfoChn
This (occasionally) leads later on to a crash.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking