Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F frama-c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 168
    • Issues 168
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • pub
  • frama-c
  • Issues
  • #1418

FRAMA_C_MALLOC_INFINITE not used in stdlib.c

ID0001214: This issue was created automatically from Mantis Issue 1214. Further discussion may take place here.


Id Project Category View Due Date Updated
ID0001214 Frama-C Plug-in > Eva public 2012-06-18 2014-02-12
Reporter Anne Assigned To yakobowski Resolution fixed
Priority normal Severity minor Reproducibility have not tried
Platform - OS - OS Version -
Product Version - Target Version - Fixed in Version Frama-C Oxygen-20120901

Description :

#define FRAMA_C_MALLOC_INFINITE #include "stdlib.c"

doesn't do what is expected since stdlib.c begins with :

#ifndef FRAMA_C_MALLOC_HEAP #ifndef FRAMA_C_MALLOC_CHUNKS #ifndef FRAMA_C_MALLOC_INDIVIDUAL #ifndef FRAMA_C_MALLOC_POSITION #define FRAMA_C_MALLOC_HEAP

so it ends up with FRAMA_C_MALLOC_HEAP instead. Is this on purpose ?

PS. I select [Kernel] category because I don't know where else to put it...

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking