Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(asar.dll) assemble error flag isn't reset #2

Closed
boldowa opened this issue Sep 3, 2017 · 4 comments
Closed

(asar.dll) assemble error flag isn't reset #2

boldowa opened this issue Sep 3, 2017 · 4 comments

Comments

@boldowa
Copy link
Contributor

boldowa commented Sep 3, 2017

This issue doesn't occur in exe

Overview

Once an compilation fails, subsequent compilation will not succeed.

steps Assemble result asar_patch() result remarks
1 OK true errordata count is 0
2 NG false errordata count isn't 0
3 OK false errordata count is 0

In [3], the result of asar_patch() should be true.

Opinion

Since this is an error as a result of the whole assembly, it may be doing this on purpose.

However, I think that Asar shouldn't be judge it. That's the role of a tool that uses it.

Cause

interface-lib.cpp line: 16 - errored

Initialization processing of this variable exists only in asar_math(). Why

@boldowa
Copy link
Contributor Author

boldowa commented Sep 3, 2017

There are 2 plans to fix it.

  1. reset "errored" when asar_reset() called
  2. reset "errored" before assemble

(Alternatively, do both of the above)

If the policy is decided, the modification will take only a few minutes.

@RPGHacker
Copy link
Owner

Thanks for the report. I'm currently setting up an environment for easily testing the Asar's DLL by running a bunch of patchs through it. I've actually encountered a bunch of bugs with it already, Once the test environment is there, I'll see if I can reproduce and fix this.

@RPGHacker
Copy link
Owner

Should be fixed with the latest commit. Can you sync and verify for me, please?

@boldowa
Copy link
Contributor Author

boldowa commented Sep 5, 2017

I confirmed it.

OK, it seems to be working fine. 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants