Bug 171591 - Segmentation fault if destination path contains a special character
Segmentation fault if destination path contains a special character
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: dos2unix (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2005-10-23 19:35 EDT by Brian Curtis
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-23 22:22:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Curtis 2005-10-23 19:35:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
The utility produces a segmentation fault when the destination path contains a special character


dos2unix -n example.cpp /cm/vobs/examplevob/example_prj/example.cpp

dos2unix -n example.cpp /cm/vobs/examplevob/example-prj/example.cpp


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

How reproducible:

Steps to Reproduce:
1.  Create example.cpp in dos format under /.
2.  Create a directory with a special character in the name (ex: /ex_ample, /ex-ample).
3.  Under /, run "dos2unix -n example.cpp /ex_ample/example.cpp"

Actual Results:  Segmentation fault

Expected Results:  Produce a UNIX format example.cpp in the destination path.

Additional info:
Comment 1 Brian Curtis 2005-10-23 22:21:57 EDT
Reproduction is a simplified example.  Bug is not always reproducable as 
originally noted, but always happends with the same file in a build script.  
It occurs several files have already be run through dos2unix and placed in a 
destination directory like \example_dir.  Issue appears to have more to do 
with NFS / ClearCase environment.

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