RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 820176 - Too much warning messages on non-existent command
Summary: Too much warning messages on non-existent command
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ltrace
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: DJ Delorie
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-09 10:46 UTC by Michal Nowak
Modified: 2015-11-13 17:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-13 17:38:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Packaging patch (4.15 KB, patch)
2015-04-15 10:16 UTC, Petr Machata
no flags Details | Diff

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


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