Bug 961495 - The Welcome Message of the memstomp Utility Contains a Typing Error
Summary: The Welcome Message of the memstomp Utility Contains a Typing Error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Developer Toolset
Classification: Red Hat
Component: memstomp
Version: DTS 2.0 RHEL 6
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: beta2
: 2.0
Assignee: Jeff Law
QA Contact: Miroslav Franc
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-09 17:59 UTC by Jaromir Hradilek
Modified: 2016-02-01 02:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-10 06:27:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Proposed patch (789 bytes, patch)
2013-05-09 18:08 UTC, Jaromir Hradilek
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1232 0 normal SHIPPED_LIVE new packages: devtoolset-2-memstomp 2013-09-10 19:30:23 UTC

Description Jaromir Hradilek 2013-05-09 17:59:28 UTC
Description of problem:
When the memstomp utility is started, it displays a welcome message with a spelling error in the word "sucessfully" (notice the missing letter "c").

Version-Release number of selected component (if applicable):
devtoolset-2-memstomp-0.1.4-7.el6.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Make sure that the devtoolset-2-memstomp package is installed:

   # yum install devtoolset-2-memstomp

2. Use the memstomp utility on a binary file of your choice, for
   example:

   $ scl enable devtoolset-2 'memstomp pwd'

Actual results:
memstomp: 0.1.4 sucessfully initialized for process pwd (pid 15299).

Expected results:
memstomp: 0.1.4 successfully initialized for process pwd (pid 15299).

Additional info:
None.

Comment 2 Jaromir Hradilek 2013-05-09 18:08:12 UTC
Created attachment 745763 [details]
Proposed patch

Comment 6 errata-xmlrpc 2013-09-10 06:27:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1232.html


Note You need to log in before you can comment on or make changes to this bug.