Invalid Command Line

Question

Invalid Command Line

aleks-zer0 opened this issue 6 years ago · comments

Python version: 2.7.15 x64
BugID Version: 2018-10-17

When fuzzing EDGE on win10 x64 version 1803(build 17134.376), sometimes this happens:

Then it waits for user to press OK, and a few more minutes later, it restarts and start generating new .html tests. Btw, i'm using the setup described on the blog: https://bugid.skylined.nl/20181017001.html

Alex · Answer 1 · Tue Oct 30 2018 02:41:40 GMT+0800 (China Standard Time)

Correction, the bug doesn't happen just sometimes, it happens in 8 out of 10 iterations. Something about UWP app debugging?

Alex · Answer 2 · Tue Oct 30 2018 02:47:37 GMT+0800 (China Standard Time)

@SkyLined @j00sean

j00sean · Answer 3 · Tue Oct 30 2018 21:07:25 GMT+0800 (China Standard Time)

it's a known issue caused by windbg. Discussed over here:
https://twitter.com/berendjanwever/status/1052469149430153216
@SkyLined is already aware of it.

Alex · Answer 4 · Tue Oct 30 2018 22:11:56 GMT+0800 (China Standard Time)

Thanks. So as i can see on the thread, no solution is found yet :(

SkyLined · Answer 5 · Tue Oct 30 2018 23:46:50 GMT+0800 (China Standard Time)

Yes: the problem is in Microsoft Debugging Tools for Windows AFAICT so I cannot fix it. I also do not know what causes it, nor do I know how to work around it.

I do have plans to allow BugId to work as a JIT debugger which should make this problem non-existent. Note that this would be a mayor code rewrite which will require quite some time to implement so don't hold your breath.

You can create a wrapper for EdgeHTML and use that; this will allow you to fuzz Edge's HTML rendering and JavaScript engines without actually using Edge. That should be faster and less error prone. I have plans to create and publish such a wrapper myself for this purpose.

j00sean · Answer 6 · Wed Oct 31 2018 05:41:37 GMT+0800 (China Standard Time)

https://github.com/j00sean/SimpleWebView

SkyLined · Answer 7 · Wed Oct 31 2018 17:51:34 GMT+0800 (China Standard Time)

I'll leave this open even if I cannot fix it as it has not been resolved and this bug might help others work around it.

Alex · Answer 8 · Thu Nov 01 2018 02:37:01 GMT+0800 (China Standard Time)

Just figured out that on fresh win10 x64 v1703.15063.608 this is not an issue and works just fine, but after updating to 1803.17134.376 it starts happening again. It seems like EDGE is the actual problem, maybe they switched it to full-UWP app or something?

j00sean · Answer 9 · Tue Nov 06 2018 10:36:42 GMT+0800 (China Standard Time)

yeah man, this annoying issue starts with April updates as i posted on other issue. Anyone has tested on 1809? I have no received the update and it's not available yet from free vms (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/). I read that this update was retired by MS. But it should be available now or very soon.

SkyLined · Answer 10 · Wed Jan 02 2019 20:31:03 GMT+0800 (China Standard Time)

Work around: I confirmed the following allows you to use BugId with Edge:

Start Edge (either in BugId or manually)
Terminate browser_broker.exe once it is started.
Terminate Edge
Start Edge in BugId.

I'll see if I can add code to do this automatically.

Alex · Answer 11 · Fri Jan 11 2019 01:44:09 GMT+0800 (China Standard Time)

Still not working for me, same message pops up. Also, immediately after killing browser_broker.exe, it spawns again :(
EDIT: After several tries, it suddenly works??? How? Will keep monitoring it to see for how long it will work.
EDIT2: Ok, it pops again :( i would really like to understand what is happening here and why it works in 1 out of 10 cases..

SkyLined · Answer 12 · Fri Jan 11 2019 05:35:51 GMT+0800 (China Standard Time)

EDIT2: Ok, it pops again :( i would really like to understand what is happening here and why it works in 1 out of 10 cases..

Oh, we all do.... we all do... :'(

SkyLined · Answer 13 · Mon Mar 04 2019 23:48:36 GMT+0800 (China Standard Time)

I think this issue no longer exists, please let me know if it does.