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 1306313 - Find causes core dump
Summary: Find causes core dump
Keywords:
Status: CLOSED DUPLICATE of bug 1305063
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: findutils
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-10 14:39 UTC by Radka Brychtova
Modified: 2016-02-11 20:35 UTC (History)
0 users

Fixed In Version: findutils-4.4.2-9.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-11 20:35:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Crash report from abrt (deleted)
2016-02-10 14:39 UTC, Radka Brychtova
no flags Details
Crash report from abrt (12.26 KB, text/plain)
2016-02-10 14:41 UTC, Radka Brychtova
no flags Details

Description Radka Brychtova 2016-02-10 14:39:16 UTC
Description of problem:
Abrt check show core dump after using find in the test on RHEL 6.8.

Version-Release number of selected component (if applicable):
pkg_name:       findutils
pkg_release:    8.el6
pkg_version:    4.4.2

kernel:         2.6.32-604.el6.x86_64


How reproducible:
Using find in some test - not 100%

Steps to Reproduce:

One of our test for cups (/CoreOS/cups/scheduler/ssl-crash ) uses find:
      find / -name a -a -name b 2>/dev/null 


Actual results:
use ./runtest.sh: line 80:  8315 Aborted      (core dumped) find / -name a -a -name b 2> /dev/null

Expected results:
No core dump

Additional info:
add attachment with abrt output

Comment 2 Radka Brychtova 2016-02-10 14:41:18 UTC
Created attachment 1122818 [details]
Crash report from abrt

Comment 3 Kamil Dudka 2016-02-10 14:48:06 UTC
I believe this is a duplicate of bug #1305063.  Could you please re-test it with findutils-4.4.2-9.el6?

Comment 5 Radka Brychtova 2016-02-10 14:52:31 UTC
Sure, I will re-test it and send you output.

Comment 6 Radka Brychtova 2016-02-11 17:19:35 UTC
This testing have problem, that the issue is not 100% reproducible, even on the same machine the test pass 4 times and the 5. is fail and then next pass again.

But it looks like, the new package may fix the problem, at least I don't find the core dump with new package.

Comment 7 Kamil Dudka 2016-02-11 20:35:31 UTC
Thank you for testing it!  I will close this bug as duplicate but feel free to reopen it in case the latest version of findutils crashes in your environment.  Sorry for the inconveniences.

*** This bug has been marked as a duplicate of bug 1305063 ***


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