Bug 723587 - Crash in broadcast_coding_history_size test
Summary: Crash in broadcast_coding_history_size test
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libsndfile
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-20 16:16 UTC by Jiri Koten
Modified: 2017-12-06 10:53 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:53:06 UTC
Target Upstream Version:


Attachments (Terms of Use)
crash output (4.67 KB, text/plain)
2011-07-20 16:16 UTC, Jiri Koten
no flags Details

Description Jiri Koten 2011-07-20 16:16:06 UTC
Created attachment 514050 [details]
crash output

Description of problem:
When running test suite which comes with libsndfile source, it fails on broadcast_coding_history_size test.

[snip]

broadcast_coding_history_size  : coding_hist_size.wav .... *** buffer overflow detected ***
: /root/rpmbuild/BUILD/libsndfile-1.0.20/tests/.libs/lt-command_test terminated
======= Backtrace: =========   
/lib64/libc.so.6(__fortify_fail+0x37)[0x363eb006a7]
/lib64/libc.so.6[0x363eafe5a0] 
/lib64/libc.so.6[0x363eafd6d4] 
/root/rpmbuild/BUILD/libsndfile-1.0.20/src/.libs/libsndfile.so.1(+0x3c12c)[0x7f115d5e712c]
/root/rpmbuild/BUILD/libsndfile-1.0.20/src/.libs/libsndfile.so.1(sf_command+0x585)[0x7f115d5b3b35]
/root/rpmbuild/BUILD/libsndfile-1.0.20/tests/.libs/lt-command_test[0x404003]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x363ea1ec9d]
/root/rpmbuild/BUILD/libsndfile-1.0.20/tests/.libs/lt-command_test[0x401729]

Version-Release number of selected component (if applicable):
libsndfile-1.0.20-3.el6_1.1

How reproducible:
100%

Steps to Reproduce:
1. build the package (rpmbuild -bc)
2. go to source dir (~/rpmbuild/BUILD/libsndfile-1.0.20/)
3. run the tests 
$ ./tests/test_wrapper.sh
  
Actual results:
crash 

Expected results:
all test passed

Additional info:
You can run only the failing test:
$ ./tests/command_test bextch

Comment 1 RHEL Program Management 2011-07-20 16:18:34 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 2 Michal Hlavinka 2011-07-21 06:32:51 UTC
I can reproduce this, thanks for reporting

Comment 3 RHEL Program Management 2012-09-07 05:01:07 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Jan Kurik 2017-12-06 10:53:06 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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