I had to switch few files from masm to jwasm (2.11) compilation recently. With many of the files, I've got the 'General Failure' error that scared me at first but I could work around all these errors quite easily. However, it's a pity that such a great tool suffers from this opaque error.
Is there any chance that this error can be analyzed according to an error dump or something and eventually fixed? I didn't look at jwasm sources but I assume this error comes from asserts that check for internal out-of-range values. Perhaps more detailed error message that includes also internal information would help you to find the sources of the most frequent failures?
Unfortunately I can't provide any of the problematic files to replicate the error for copyright and other reasons.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had to switch few files from masm to jwasm (2.11) compilation recently. With many of the files, I've got the 'General Failure' error that scared me at first but I could work around all these errors quite easily. However, it's a pity that such a great tool suffers from this opaque error.
Is there any chance that this error can be analyzed according to an error dump or something and eventually fixed? I didn't look at jwasm sources but I assume this error comes from asserts that check for internal out-of-range values. Perhaps more detailed error message that includes also internal information would help you to find the sources of the most frequent failures?
Unfortunately I can't provide any of the problematic files to replicate the error for copyright and other reasons.