Opened 10 years ago
Closed 10 years ago
Last modified 5 years ago
#8473 closed Bug report (outdated)
File corruption when transfering file to QNX Neutrino Host
|Reported by:||protomok||Owned by:|
|Component version:||Operating system type:||Windows|
|Operating system version:||Windows 7, Mac OS X 10.6.8|
I've found a reproducible issue regarding corruption when transferring files.
How to reproduce:
1) Install FileZilla 126.96.36.199 client on Mac or Windows 7 - both reproduce this issue.
2) Install QNX Neutrino 6.5.0 SP1 OS in a VM or native on an x86 machine. Easiest way is to download the Virtual Machine posted here: http://www.qnx.com/download/group.html?programid=20905.
Once QNX is installed, edit /etc/inetd.conf and uncomment the line of text beginning with "ftp". Then run "inetd" if it is not already running. Also note the IP address.
3) Open FileZilla client and transfer the attached binary file "helloworld" to the FTP server running on the QNX host.
4) Checksum the file (cksum utility) before and after transferring. You'll see that the checksum is different!
5) You can copy the file from QNX back to your machine by tarring the file, e.g. "tar cvf helloworld.tar helloworld" then using FileZilla to transfer the file, or by using any FTP client other than FileZilla to ensure the file doesn't get corrupted a second time. You can then hex dump the files to see the specific differences before and after the corruption.
- I've used other FTP clients before, never seen this problem. For example from a Mac you can use the built in ftp client and there is no corruption.
- I tried copying the same file to an Ubuntu 10.04 Virtual Machine running vsftpd but the corruption did not occur.
- I created the helloworld file by writing a C file which prints hello world and compiling using the QNX toolchain. There's got to be other files that reproduce this issue but I haven't found any others yet.
Change History (5)
by , 10 years ago
by , 10 years ago
File after corruption occurs
comment:1 by , 10 years ago
|Status:||new → moreinfo|
Please provide logs. Are you sure you transferred the file using binary mode (TYPE I)?
comment:2 by , 10 years ago
|Status:||moreinfo → closed|
No reply for more than 28 days.
comment:3 by , 5 years ago
This happens to us all the time as well. It works if we use binary mode, but with Transfer type Auto it seems to corrupt the QNX 6.6 binaries. Why the Auto transfer type does not detect it is QNX ELF binary?