Bug 820176

Summary: Too much warning messages on non-existent command
Product: Red Hat Enterprise Linux 6 Reporter: Michal Nowak <mnowak>
Component: ltraceAssignee: DJ Delorie <dj>
Status: CLOSED WONTFIX QA Contact: qe-baseos-tools-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3CC: law, mcermak, mnewsome, ohudlick
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-13 17:38:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Packaging patch none

Description Michal Nowak 2012-05-09 10:46:20 UTC 
Description of problem:

$ ltrace sdsd
Can't execute `sdsd': No such file or directory
I consistently fail to read a word from the freshly launched process.
I'll now try to proceed with tracing, but this shouldn't be happening.
PTRACE_SETOPTIONS: No such process
ltrace: Couldn't find .dynsym or .dynstr in "sdsd"

Version-Release number of selected component (if applicable):

ltrace-0.5-23.45svn.el6.x86_64

Expected results:

I somehow think there are too much warnings. The first one seems to me enough.
Comment 2 RHEL Program Management 2012-05-13 04:03:56 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 6 Petr Machata 2015-04-15 10:16:58 UTC 
Created attachment 1014667 [details]
Packaging patch

This includes both the primary patch as well as the spec patch.
Comment 9 Matt Newsome 2015-11-13 17:38:43 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux. We've carefully evaluated the request, but are unable to include it in a future release as Red Hat Enterprise Linux 6 moves towards production phase 2[*].

To request that Red Hat re-consider this request, please re-open the bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

[*] https://access.redhat.com/support/policy/updates/errata