Downloads:

4,083

Downloads of v 6.6.5:

325

Last Update:

7/9/2019

Package Maintainer(s):

Software Author(s):

  • Resplendence Software Projects Sp.

Tags:

Crash Dump Debugging

Who Crashed

6.6.5 | Updated: 7/9/2019

Downloads:

4,083

Downloads of v 6.6.5:

325

Maintainer(s):

Software Author(s):

  • Resplendence Software Projects Sp.

Who Crashed 6.6.5

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Who Crashed, run the following command from the command line or from PowerShell:

>

To upgrade Who Crashed, run the following command from the command line or from PowerShell:

>

To uninstall Who Crashed, run the following command from the command line or from PowerShell:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade whocrashed -y --source="'STEP 3 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 whocrashed -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure whocrashed installed
  win_chocolatey:
    name: whocrashed
    state: present
    version: 6.6.5
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'whocrashed' do
  action    :install
  version  '6.6.5'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: whocrashed,
    Version: 6.6.5,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller whocrashed
{
   Name     = 'whocrashed'
   Ensure   = 'Present'
   Version  = '6.6.5'
   Source   = 'STEP 3 URL'
}

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


package { 'whocrashed':
  provider => 'chocolatey',
  ensure   => '6.6.5',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install whocrashed version="6.6.5" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 7/10/2019.

Description

Note:

    The Free edition is only available for home use. Business users must purchase a professional license.

    Analyzes existing crash dumps and tries to determine and state the root cause in easy to understand language.

tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$checksum = '0A7E3A03256D3143118BE5389F0C5F7F405A40066D999E246C57280E9282AE14'
$url = 'http://www.resplendence.com/download/whocrashedSetup.exe'

$packageArgs = @{
  packageName   = 'whocrashed'
  unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  fileType      = 'exe'
  url           = $url
  silentArgs    = '/VERYSILENT /NORESTART'
  validExitCodes= @(0, 3010, 1641)
  softwareName  = 'WhoCrashed*'
  checksum      = $checksum
  checksumType  = 'sha256'
}

Install-ChocolateyPackage @packageArgs

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.

Version Downloads Last Updated Status
Who Crashed 6.6.1 201 Monday, June 3, 2019 Approved
Who Crashed 6.6.0 420 Saturday, February 23, 2019 Approved
Who Crashed 6.5.0 211 Tuesday, January 22, 2019 Approved
Who Crashed 6.01 1290 Saturday, July 7, 2018 Approved
Who Crashed 5.53 1121 Sunday, November 6, 2016 Approved
Who Crashed 5.03 515 Friday, January 15, 2016 Approved

This package has no dependencies.

Discussion for the Who Crashed Package

Ground Rules:

  • This discussion is only about Who Crashed and the Who Crashed 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 Who Crashed, 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