Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 136148 - missing return statement
missing return statement
Product: Fedora
Classification: Fedora
Component: dos2unix (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2004-10-18 07:46 EDT by David Binderman
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version: 3.1-21
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-20 11:30:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:195 low SHIPPED_LIVE dos2unix and unix2dos bug fix update 2005-05-19 00:00:00 EDT

  None (edit)
Description David Binderman 2004-10-18 07:46:21 EDT
Description of problem:

I just tried to compile package dos2unix-3.1-19 from package
Redhat Fedora Core 3 Test 3.

The compiler said

dos2unix.c(172): warning #1011: missing return statement at end of
non-void function "StripDelimiter"

The source code is

  if (ipFlag->NewLine) {  /* add additional LF? */
    putc('\n', ipOutF);

But the function is marked with "int" return type. Suggest add a
return statement to the end of the function.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Miloslav Trmač 2004-10-20 11:30:55 EDT
Fixed in dos2unix-3.1-21. Thanks for your report.
Comment 2 Tim Powers 2005-05-19 20:35:36 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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