Downloads:

14,137

Downloads of v 2.5.0:

441

Last Update:

03 Nov 2021

Package Maintainer(s):

Software Author(s):

  • VMWare
  • Google

Tags:

admin drmemory memory profiler dev debugging fuzz multi-platform

Dr. Memory

  • 1
  • 2
  • 3

2.5.0 | Updated: 03 Nov 2021

Downloads:

14,137

Downloads of v 2.5.0:

441

Maintainer(s):

Software Author(s):

  • VMWare
  • Google

  • 1
  • 2
  • 3
Dr. Memory 2.5.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Dr. Memory, run the following command from the command line or from PowerShell:

>

To upgrade Dr. Memory, run the following command from the command line or from PowerShell:

>

To uninstall Dr. Memory, run the following command from the command line or from PowerShell:

>

Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade drmemory -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade drmemory -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install drmemory
  win_chocolatey:
    name: drmemory
    version: '2.5.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'drmemory' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.5.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller drmemory
{
    Name     = "drmemory"
    Version  = "2.5.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'drmemory':
  ensure   => '2.5.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 03 Nov 2021.

Description

Dr. Memory is a memory monitoring tool capable of identifying memory-related programming errors such as accesses of uninitialized memory, accesses to unaddressable memory (including outside of allocated heap units and heap underflow and overflow), accesses to freed memory, double frees, memory leaks, and (on Windows) access to un-reserved thread local storage slots.

Dr. Memory operates on unmodified application binaries running on Windows or Linux on commodity IA-32 and AMD64 hardware. Dr. Memory currently targets 32-bit applications only.

Dr. Memory is built on the DynamoRIO dynamic instrumentation tool platform.


Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Dr. Memory 2.4.0 173 Friday, September 3, 2021 Approved
Dr. Memory 2.3.1860910 1397 Monday, December 14, 2020 Approved
Dr. Memory 2.3.18351 1544 Monday, March 30, 2020 Approved
Dr. Memory 2.3.18322 191 Sunday, March 8, 2020 Approved
Dr. Memory 2.3.0 192 Friday, February 7, 2020 Approved
Dr. Memory 2.2.0 554 Monday, August 26, 2019 Approved
Dr. Memory 2.1.17972 466 Friday, April 26, 2019 Approved
Dr. Memory 2.0.17959 463 Monday, March 11, 2019 Approved
Dr. Memory 1.11.0 2365 Sunday, July 9, 2017 Approved
Dr. Memory 1.8.0.8 5711 Thursday, January 1, 2015 Approved
Dr. Memory 1.6.1.2 640 Tuesday, February 11, 2014 Approved
Discussion for the Dr. Memory Package

Ground Rules:

  • This discussion is only about Dr. Memory and the Dr. Memory package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Dr. Memory, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus