Disk full shows no error and displays "0 bytes"

Index > Compiler Internals > Disk full shows no error and displays "0 bytes"

Author

Thread

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 02:32

As the picture shows

Description:
Filesize:	12.31 KB
Viewed:	12656 Time(s)

22 Mar 2015, 02:32

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20338
Location: In your JS exploiting you and your system

revolution 22 Mar 2015, 02:38

I see a different result with 1.71.39.

Perhaps if you downloaded the latest version it will fix your problem?

Description:
Filesize:	12.47 KB
Viewed:	12653 Time(s)

22 Mar 2015, 02:38

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 02:39

revolution wrote:

I see a different result with 1.71.39.

Perhaps if you downloaded the latest version it will fix your problem?

You didn't know that my disk was full...Deleting sonething it's OK

22 Mar 2015, 02:39

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20338
Location: In your JS exploiting you and your system

revolution 22 Mar 2015, 02:43

I changed the title to reflect the actual problem.

22 Mar 2015, 02:43

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 02:47

If the assembly file can be written normally it says write failed

22 Mar 2015, 02:47

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 02:50

And if there is 4KB storage and the .asm file is bigger than 4KB even if all comments it says write failed

22 Mar 2015, 02:50

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 03:54

If the .asm file is locked compiling it gives a window asking where to put it but if still choose this file it compile as still
revolution you may try this case

22 Mar 2015, 03:54

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 8353
Location: Kraków, Poland

Tomasz Grysztar 22 Mar 2015, 10:23

l4m2 wrote:

As the picture shows

This must have been caused by the fact that fasmw did not correctly report an error that occurred during the WriteFile, and so it called fasm on a source file that was empty (because writing the source from editor failed), hence the "0 bytes". I'm uploading the corrected fasmw that should handle write errors of this kind in a better manner.

22 Mar 2015, 10:23

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 10:34

Tomasz Grysztar wrote:

l4m2 wrote:
As the picture shows
This must have been caused by the fact that fasmw did not correctly report an error that occurred during the WriteFile, and so it called fasm on a source file that was empty (because writing the source from editor failed), hence the "0 bytes". I'm uploading the corrected fasmw that should handle write errors of this kind in a better manner.

So why error when writing a space-fulfilled .asm?

22 Mar 2015, 10:34

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 8353
Location: Kraków, Poland

Tomasz Grysztar 22 Mar 2015, 10:51

l4m2 wrote:

So why error when writing a space-fulfilled .asm?

fasmw saves the current source file (and also files from the other tabs if they were modified) and then calls fasm, which in turn loads source text from this file, assembles it, and saves the output. There are many disk operations that can fail during this process, especially when you are running out of disk space. But the bug here was that fasmw reported successful assembly while there were some writes that failed - this is what I intended to fix.

22 Mar 2015, 10:51

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 10:54

I meant a big file with nothing to compile

22 Mar 2015, 10:54

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 8353
Location: Kraków, Poland

Tomasz Grysztar 22 Mar 2015, 11:04

As I wrote above, there are many disk operations during this process that may fail for various reasons. Do you mean that fasmw should ask WinAPI for a more detailed report on what error happened and display it instead of simply acknowledging that the write operation failed? It would probably be ERROR_HANDLE_DISK_FULL or ERROR_DISK_FULL in this case.

22 Mar 2015, 11:04

l4m2

Joined: 15 Jan 2015
Posts: 674

l4m2 22 Mar 2015, 12:33

Tomasz Grysztar wrote:

As I wrote above, there are many disk operations during this process that may fail for various reasons. Do you mean that fasmw should ask WinAPI for a more detailed report on what error happened and display it instead of simply acknowledging that the write operation failed? It would probably be ERROR_HANDLE_DISK_FULL or ERROR_DISK_FULL in this case.

Needn't.
FASM mean to make a small compiler doesnt it?(Maybe optional?)

22 Mar 2015, 12:33

< Last Thread | Next Thread >

Forum Rules:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum