You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi WSL Team,
thanks a lot for the cool features wsl brings to Windows.
I am assessing syscall behaviour of wsl for my bachelor thesis.
As I dont know whats going on down in the wsl kernel this might be a bug, security feature, translation error, simply work as intended or even my fault. Since I can't tell I thought I share that with you.
Microsoft Windows [Version 10.0.16299.309]
I wrote a small C program, which takes a syscallid as argument, moves it to eax and performes an interrupt. This is realized through inline asm:
As far as I was able to interpret the lxcore_kernel.elt trough vi there was a message like asmLxpSigInfoFromException Unhandled exception code 0x10000001 but I haven't inspected it further yet.
The text was updated successfully, but these errors were encountered:
Hi WSL Team,
thanks a lot for the cool features wsl brings to Windows.
I am assessing syscall behaviour of wsl for my bachelor thesis.
As I dont know whats going on down in the wsl kernel this might be a bug, security feature, translation error, simply work as intended or even my fault. Since I can't tell I thought I share that with you.
Microsoft Windows [Version 10.0.16299.309]
I wrote a small C program, which takes a syscallid as argument, moves it to eax and performes an interrupt. This is realized through inline asm:
Execution on Linux:
Exits always with 0 and errno set like the following.
Execution on WSL:
Exits always with 1 after
write(1, syscallid...
or on the interrupt.As far as I was able to interpret the lxcore_kernel.elt trough vi there was a message like
asmLxpSigInfoFromException Unhandled exception code 0x10000001
but I haven't inspected it further yet.The text was updated successfully, but these errors were encountered: