Binary

[timea-techgirl]

Hello,
Can you please add the compiled binary as many people don't know how to do it? I'm not a programmer.

I figured it out somehow and built with c11 standard but the program crashes.

I have 3 files.
data.ext4.win000 (1.53GB)
data.ext4.win001 (1.48GB)
data.ext4.win002 (224MB)

When I use the command on the first file, the program crashes. The first file is the corrupted one because I get the extractTarFork() process ended with ERROR: 255 TWRP error exactly at 44 percent.

C:\Users\Mali\Desktop\2018-09-25--02-48-15_M4B30Z>CleanTwrpTar -v data.ext4.win000 fixed.tar
Proceeding without strings file.
Block Position: 3081601 Next: 3081603 Size: 52 (1 blocks)
Offset: 2422784 Global Offset: 0
Size of strings found in before header: 0
String clusters found in file: 0 (Size: 0)
New string stringcluster size: 0
"CRASH"

The other two files aren't corrupted, so the program doesn't crash.
The other utility TarCleaner successfully found 2 leaks and fixed it.

Please fix this. Thank you!

[BuildingAtom]

Alright, I'll get a binary up with my next revision, and I'll look deeper into the crash when I get a chance to do so, hopefully this weekend. I saw your other post, and I'm glad this work we did was helpful. In the end, because this code was originally made for the informal "competition," there are a lot of problems with this as it stands, and I suggest using the other utility first because I don't have as much time to fix and maintain this as much as I would like.

Also, do you by any chance know if you compiled for 32-bit or 64-bit?

[timea-techgirl]

I used this command, "gcc.exe input.c -o output.exe"
I installed using the 64 bit installer.

[BuildingAtom]

Sorry for the late follow up, I stopped receiving notifications for whatever reason. Is the output above the complete output? It seems like I will first be adding additional logging so it is easier to identify where the crash is occurring.
Also, do you know/could you check which gcc compiler version you used? You can check this using the command: gcc --version. Did you include -std=c11 by any chance? This shouldn't matter because past some version of gcc, an extension of the C11 standard is used as default, and I do not remember it being able to compile when the wrong standard is used, but I could be remembering wrong.

Just in case, could you try compiling with gcc.exe -std=c11 input.c -o output.exe to see if that changes anything?

[timea-techgirl]

Oh my message seems to be incomplete. I did build with c11 standard with gcc.exe -std=c11 input.c -o output.exe and the crash still occurred. I have the corrupted file to test as much as you like.

I installed with the mingw online installer. I'll tell you the exact version when I get home.

But why don't you send your binary so that I can see if it crashes... You can add the logging too.

[timea-techgirl]

So, I used two compilers. The first one's version was 5.1 and the second one was 6.3

[BuildingAtom]

So it turns out there is a binary on the releases page. Could you give that a shot anyway? I'm not expecting much will change, but who knows. I'll be making a logging version and putting it up here in a bit (probably a few hours tbh). Thank you for sticking with this issue.

[timea-techgirl]

Thank you for the quick reply. I just checked. My compilation was of the same size. Hence, it crashed again.

[BuildingAtom]

Attached is a version I compiled with some preliminary form of logging functionality built in.
CleanTwrpTar.exe -v -l logfile.txt [inputfile] [outputfile]

Binary w-logging.zip

The logging is pretty much thrown in there, but it'll help me narrow down the problem.

[timea-techgirl]

logfile.txt
Nothing in the log. :(

[BuildingAtom]

That's very weird... It just cuts off abruptly....

That makes me think its a bigger problem with it either leaking a ton of memory, the program running out of memory, or windows just thinking the program is unresponsive and "crashing" it when it isn't.

When it crashes, does it just straight up crash, or does it say "unresponsive?" If it's the latter, could you try just running and letting it go, or running the program below? I just made the verbose messages even more verbose (it's ugly though).
CleanTwrpTar - extremely verbose.zip

[timea-techgirl]

Yes. I checked memory in task manager. It didn't seem to increase.

[BuildingAtom]

My bad, I just realized that I forgot to disable buffering on log file output, so try this instead.

Binary w-logging.zip

[timea-techgirl]

[CLEAN] Clean file copy, size 1
	[CLEAN] Copied 1 blocks of 1
[CLEAN] Clean file copy, size 2
	[CLEAN] Copied 2 blocks of 2
[CLEAN] Clean file copy, size 37810
	[CLEAN] Copied 37810 blocks of 37810
[CLEAN] Clean file copy, size 2
	[CLEAN] Copied 2 blocks of 2
Possible leaked strings.
	Copying next header and any continuous data before without leaks. 2960010 to 3081601 with offset 2422784
	Copied 121592 blocks of 121592
	Block Position: 3081601	Next: 3081603	Size: 52 (1 blocks)
	Offset: 2422784	Global Offset: 0
	Size of strings found in before header: 0
	String clusters found in file: 0 (Size: 0)
	New string stringcluster size: 0

[CLEAN] Clean file copy, size 2
	[CLEAN] Copied 2 blocks of 2
[CLEAN] Clean file copy, size 1
	[CLEAN] Copied 1 blocks of 1
[CLEAN] Clean file copy, size 2
	[CLEAN] Copied 2 blocks of 2
[CLEAN] Clean file copy, size 1
	[CLEAN] Copied 1 blocks of 1
[CLEAN] Clean file copy, size 2
	[CLEAN] Copied 2 blocks of 2
[CLEAN] Clean file copy, size 1
	[CLEAN] Copied 1 blocks of 1
[CLEAN] Clean file copy, size 2
	[CLEAN] Copied 2 blocks of 2
Possible leaked strings.

Crash after the above.