Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pikelang
  • pikepike
  • Issues
  • #2363
Closed
Open
Issue created Oct 04, 2001 by Peter Bortas@zinoOwner

configure --without-dmalloc doesn't work.

Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=2363

Reported by @grubba

From: John W Pierce <jwp@ucsd.edu>
To: "pike@roxen.com" <pike@roxen.com>
Date: Wed, 3 Oct 2001 14:09:57 -0700
Subject: RE: v7.3 - verbose_debug_exit is set  unconditionally in
pike_memory.c

From: Henrik Grubbström [mailto:grubba@roxen.com]

Hmm, looks like you've compiled with dmalloc...

Below is the configuration used.

configure --prefix=/usr/local \
    --with-include-path="$CPPFLAGS" \
    --with-double-precision \
    --with-int-int \
    --with-oob \
    --with-security \
    --with-shared-nodes \
    --without-cdebug \
    --without-debug \
    --without-dmalloc \
    --without-dmalloc-malloc \
    --without-rtldebug \
    --without-thread-trace

You are correct, however, that DEBUG_MALLOC is defined in machine.h after configuration, even though should explicitly prevent that.

Assignee
Assign to
Time tracking