Anyone interested in my ioFTPD build?

UltraFine · 11-26-2018, 08:44 AM

Quote:

Originally Posted by Prodigy

In the event of waiting Yil comes back and ioFTPD v8? and my noob attempt to mastering C. I have made some modifications based on vanilla ioFTPD v7.7.3 :

Compiled with Visual Studio 2015 Update 2 with windows XP compatibility (not tested)
Fixed some warning found when compiling
Fixed some null pointer based on static analysis by PVS-STUDIO
Upgraded TCL into 8.5.19
Upgraded into OpenSSL 1.02g, disabled SSLV2 and upgraded to TLS v1.2
Fixed freeing null pointer in some cases (PVS-STUDIO)
Added some null pointer check.

Currently i have tested on minimal testing environment (local transfer) and LAN transfer, with 0 script addon. I am not recommended to run it on production without further testing.

Does anyone interested in this?, of course i will also sharing the source code.

Hi Prodigy, very happy to see that you managed to compile the code.

I tried your version on two completly different machines: WIN7 and WIN10. On both machines sticking any sctipt (ioBanana, ioA) in the SCHEDULER makes ioftpd crash. (I tried newday and searchlog by ioA 2.0.5).

On both mashies it crashes with:

Code:

Unhandled exception: Access Violation (0xC0000005)
Address: 0x013F0B0C [attempting to write data to 0x00000005]

YILs version seems to work just fine with the SCHEDULER.

Ultra

Prodigy · 11-30-2018, 08:14 AM

Quote:

Originally Posted by UltraFine

Hi Prodigy, very happy to see that you managed to compile the code.

I tried your version on two completly different machines: WIN7 and WIN10. On both machines sticking any sctipt (ioBanana, ioA) in the SCHEDULER makes ioftpd crash. (I tried newday and searchlog by ioA 2.0.5).

On both mashies it crashes with:

Code:

Unhandled exception: Access Violation (0xC0000005)
Address: 0x013F0B0C [attempting to write data to 0x00000005]

YILs version seems to work just fine with the SCHEDULER.

Ultra

[Edit]
Reverted my changes, only plain mr-b's change, and other required changes in other to compile. Test it again.

UltraFine · 12-15-2018, 04:08 AM

Hello Prodigy,

I tried the new version this night and both schedule events in it caused ioftpd to crash, just as in the previous version that you had posted here. Both events work with YIL version. Unfortunatly YIL version does not work with the new SSL libraries (as far as I can tell).

Do you want me to send you the crash dumps?

Code:

Sat Dec 15 04:00:07 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x01040B0C [attempting to write data to 0x00000007]
PID=6340, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 17200

System information:
<removed>
Notice: Unable to acquire Debug Rights

Code:

Sat Dec 15 00:10:14 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x01040B0C [attempting to write data to 0x00000008]
PID=22396, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 16436

System information:
<removed>
OS: Windows 6.2 (build 9200)
Registry: Windows 10 Enterprise
Decoded: Vista
Page size: 4096
Notice: Unable to acquire Debug Rights

Here is my scheduler setup:

Code:

[Scheduler]
Reset           = 0 0 * *                  &Reset
ConfigUpdate    = 0,10,20,30,40,50 * * *   &ConfigUpdate
Newday = 10 23 * * EXEC ..\scripts\ioA\ioA.exe NEWDATE
searchlog = 0 3 * * EXEC ..\scripts\ioA\ioA.exe SEARCHLOGCREATE

UltraFine · 12-15-2018, 04:10 AM

Prodigy, one more thing:

it would be awesome you could tagg your versions somehow diffrently. I get confused with the exe files because they also have the same version tag as the YIL version. Also in the crash-log it writes 7.7.3 and you never know if you tested the correct version. Maybe change the version tag to 7.7.3.p1 , 7.7.3.p2 etc.

Cheers
UltraFine

Prodigy · 12-15-2018, 05:21 AM

Quote:

Originally Posted by UltraFine

Prodigy, one more thing:

it would be awesome you could tagg your versions somehow diffrently. I get confused with the exe files because they also have the same version tag as the YIL version. Also in the crash-log it writes 7.7.3 and you never know if you tested the correct version. Maybe change the version tag to 7.7.3.p1 , 7.7.3.p2 etc.

Cheers
UltraFine

Will do soon, if we manage to tackle those error.

Prodigy · 12-15-2018, 05:20 AM

Quote:

Originally Posted by UltraFine

Hello Prodigy,

I tried the new version this night and both schedule events in it caused ioftpd to crash, just as in the previous version that you had posted here. Both events work with YIL version. Unfortunatly YIL version does not work with the new SSL libraries (as far as I can tell).

Do you want me to send you the crash dumps?

Code:

Sat Dec 15 04:00:07 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x01040B0C [attempting to write data to 0x00000007]
PID=6340, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 17200

System information:
<removed>
Notice: Unable to acquire Debug Rights

Code:

Sat Dec 15 00:10:14 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x01040B0C [attempting to write data to 0x00000008]
PID=22396, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 16436

System information:
<removed>
OS: Windows 6.2 (build 9200)
Registry: Windows 10 Enterprise
Decoded: Vista
Page size: 4096
Notice: Unable to acquire Debug Rights

Here is my scheduler setup:

Code:

[Scheduler]
Reset           = 0 0 * *                  &Reset
ConfigUpdate    = 0,10,20,30,40,50 * * *   &ConfigUpdate
Newday = 10 23 * * EXEC ..\scripts\ioA\ioA.exe NEWDATE
searchlog = 0 3 * * EXEC ..\scripts\ioA\ioA.exe SEARCHLOGCREATE

Hmm, that's strange, if i remembering it right the crashes is only happened if there is encoding directory inside the lib/tcl8.5 dir..., could you please check it out if there is that directory inside the lib/tcl8.5/ dir?, it was included in old of my build archive if i am not mistaken, perhaps you still have it. So just delete that encoding directory.

UltraFine · 12-16-2018, 07:59 AM

Hello Prodigy,

this night I tried it again, removed encoding directory and double checked that I take the right exe file. It still crashes on SCHEDULER.

ioftpd.exe size: 685 KB (701.440 Bytes) from ‎30. ‎November ‎2018, ‏‎14:45:53

interestingly:
TINYDUMP-20181216.040042-24524.dmp is of size 0.
TINYDUMP-20181216.001047-16920.dmp is of size 0.

Code:

Sun Dec 16 00:10:47 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x00BF1895 [attempting to read data from 0x00000009]
PID=16920, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 22672

System information:
<CPU info remoeved>
OS: Windows 6.2 (build 9200)
Registry: Windows 10 Enterprise
Decoded: Vista
Page size: 4096
Notice: Unable to acquire Debug Rights

Code:

Sun Dec 16 04:00:42 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x00BF1895 [attempting to read data from 0x00000007]
PID=24524, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 20140

System information:
<CPU info removed>
OS: Windows 6.2 (build 9200)
Registry: Windows 10 Enterprise
Decoded: Vista
Page size: 4096
Notice: Unable to acquire Debug Rights

Do you want to see the MINIDUMP-20181216.040042-24524.dmp and MINIDUMP-20181216.001047-16920.dmp files?

UltraFine

P.S. I am not sure, but isnt it possible that this crashes have something to do with the variables set in ioftpd.env ?

Here are mine:

Code:

ACCSPEED=%.4[speed]
COMSPEC=%[environment(COMSPEC)]
CREDITS=%[credits(mega)]
CREDITSECTION=%[$creditsection]
FLAGS=%[$flags]
GID=%[$gid]
GROUP=%[$group]
GROUPS=%[group]
IDENT=%[$ident]
IP=%[$ip]
PATH=%[$path]
PWD=%[$pwd]
REALPATH=%[environment(PATH)]
SECTION=%[$sectionid]
SPEED=%.[speed]
STATSSECTION=%[$statssection]
SYSTEMDRIVE=%[environment(SYSTEMDRIVE)]
SYSTEMPATH=%[$path]
SYSTEMROOT=%[environment(SYSTEMROOT)]
TAGLINE=%[$unfo]
UID=%[$uid]
USER=%[$user]
VIRTUALPATH=%[$pwd]
WINDIR=%[environment(WINDIR)]

Prodigy · 12-18-2018, 01:24 PM

Hmm, looks like unable to access 0xC0000005 is pretty generic one on windows, one of the reason is faulty hardware or windows installation, if that's the case it should also happened with Yil one.

My assembly language is pretty rusty, but it would be helpful if you give me the complete setup in which the case is happened.

Mean while, could you please trying the following to disable DEP on ioFTPD.exe ?, steps are in here.

UltraFine · 12-20-2018, 07:58 AM

Quote:

Originally Posted by Prodigy

Hmm, looks like unable to access 0xC0000005 is pretty generic one on windows, one of the reason is faulty hardware or windows installation, if that's the case it should also happened with Yil one.

My assembly language is pretty rusty, but it would be helpful if you give me the complete setup in which the case is happened.

Mean while, could you please trying the following to disable DEP on ioFTPD.exe ?, steps are in here.

Prodigy, just for your interest: I have tried to disable DEP for ioftpd.exe (to put it into the excluded list) and my win7 does not go for it. I get a message that exluding this program from DEP is impossible. DEP has to be run for this program.