I am trying to dump IDT, and this is what I get:
0: kd> !idt
Dumping IDT: 80f27000
30: 82127570 nt!KiUnexpectedInterrupt0Shadow
31: 82127580 nt!KiUnexpectedInterrupt1Shadow
32: 82127590 nt!KiUnexpectedInterrupt2Shadow
33: 821275a0 nt!KiUnexpectedInterrupt3Shadow
34: 821275b0 nt!KiUnexpectedInterrupt4Shadow
35: 821275c0 nt!KiUnexpectedInterrupt5Shadow
36: 821275d0 nt!KiUnexpectedInterrupt6Shadow
Running on Win 10 x86.
How can I see the "normal" IDT?
Thanks in advance.
Edit:
When I say normal I mean something like this:
31: 80dd816c i8042prt!I8042KeyboardInterruptService (KINTERRUPT 80dd8130)
32: 804ddd04 nt!KiUnexpectedInterrupt2
33: 80dd3224 serial!SerialCIsrSw (KINTERRUPT 80dd31e8)
34: 804ddd18 nt!KiUnexpectedInterrupt4
35: 804ddd22 nt!KiUnexpectedInterrupt5
36: 804ddd2c nt!KiUnexpectedInterrupt6
37: 804ddd36 nt!KiUnexpectedInterrupt7
38: 806edef0 hal!HalpProfileInterrupt```
It was KVA Shadowing that was making me a problem. I fixed it by disabling Spectre and Meltdown vulnerabilities.
Edit:
You can download program form here: https://www.grc.com/inspectre.htm and just disable it, or you can go to registry and changes some values more about that here: https://www.unknowncheats.me/forum/anti-cheat-bypass/360795-disable-kvashadowing-1809-1903-windows.html. But changing registry didn't work for me on latest win 10. So just download inspectre and disable it, should be no problem.
Related
I am seeing the following error from the console window on VSC.
ERROR: Unable to start debugging. Unexpected LLDB output from command "-exec-run". process exited with status -1 (attach failed ((os/kern) invalid argument))
The program '/Users/torsi/vsc-workspace/Helloworld' has exited with code 42 (0x0000002a).
But if I run lldb from the command-line the application is fully debuggable.
I believe this is an entitlement issue having to do with these two required entitlements
that I verified are not set for the VSC applications. I used codesign to verify the entitlements for the application by reference the .app directory of VSC.
<key>com.apple.security.network.client</key>
<key>get-task-allow</key>
Here is the logging output from lldb:
1: (245) LaunchOptions{"name":"clang++ - Build and debug active file","type":"cppdbg","request":"launch","targetArchitecture":"arm64","program":"/Users/torsi/vsc-workspace/Helloworld","args":[],"stopAtEntry":true,"cwd":"/Users/torsi/vsc-workspace","environment":[],"externalConsole":false,"MIMode":"lldb","preLaunchTask":"clang++ build active file","logging":{"engineLogging":true},"__configurationTarget":5,"__sessionId":"7b7e7bcf-4626-413b-aec8-0b1bf19605b9","miDebuggerPath":"/Users/torsi/.vscode/extensions/ms-vscode.cpptools-1.3.1/debugAdapters/lldb-mi/bin/lldb-mi"}
1: (420) Starting: "/Users/torsi/.vscode/extensions/ms-vscode.cpptools-1.3.1/debugAdapters/lldb-mi/bin/lldb-mi" --interpreter=mi
1: (485) DebuggerPid=39408
1: (506) ->(gdb)
1: (549) <-1001-interpreter-exec console "version"
1: (551) ->~"lldb-1200.0.44.2\nApple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1200.0.32.28)\n"
1: (553) ->1001^done
1: (554) ->(gdb)
1: (564) 1001: elapsed time 17
1: (571) <-1002-gdb-set auto-solib-add on
1: (572) ->1002^done
1: (572) ->(gdb)
1: (578) 1002: elapsed time 7
1: (580) <-1003-gdb-set solib-search-path "/Users/torsi/vsc-workspace:"
1: (580) ->1003^done
1: (580) ->(gdb)
1: (580) 1003: elapsed time 0
1: (581) <-1004-environment-cd /Users/torsi/vsc-workspace
1: (581) ->1004^done,path="/Users/torsi/vsc-workspace"
1: (581) ->(gdb)
1: (585) 1004: elapsed time 4
1: (585) <-1005-file-exec-and-symbols /Users/torsi/vsc-workspace/Helloworld
1: (811) ->1005^done
1: (811) ->(gdb)
1: (811) ->=library-loaded,id="/Users/torsi/vsc-workspace/Helloworld",target-name="/Users/torsi/vsc-workspace/Helloworld",host-name="/Users/torsi/vsc-workspace/Helloworld",symbols-loaded="1",symbols-path="/Users/torsi/vsc-workspace/Helloworld.dSYM/Contents/Resources/DWARF/Helloworld",loaded_addr="-",size="16384"
1: (811) 1005: elapsed time 226
1: (812) <-1006-interpreter-exec console "platform status"
1: (812) ->~" Platform: host\n Triple: x86_64-apple-macosx\nOS Version: 10.16 (20D80)\n Kernel: Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101\n Hostname: 127.0.0.1\nWorkingDir: /Users/torsi/vsc-workspace\n"
1: (812) ->1006^done
1: (813) ->(gdb)
1: (818) 1006: elapsed time 6
1: (821) <-1007-break-insert -f main
1: (823) ->1007^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000000100003f60",func="main",file="Helloworld.cpp",fullname="/Users/torsi/vsc-workspace/Helloworld.cpp",line="8",pending=["main"],times="0",original-location="main"}
1: (823) ->(gdb)
1: (823) ->=breakpoint-modified,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000000100003f60",func="main",file="Helloworld.cpp",fullname="/Users/torsi/vsc-workspace/Helloworld.cpp",line="8",pending=["main"],times="0",original-location="main"}
1: (823) ->(gdb)
1: (828) 1007: elapsed time 7
1: (847) Send Event AD7EngineCreateEvent
1: (852) Send Event AD7ProgramCreateEvent
1: (895) Send Event AD7LoadCompleteEvent
1: (902) <-1008-exec-run
1: (5954) ->1008^error,msg="process exited with status -1 (attach failed ((os/kern) invalid argument))"
1: (5955) ->(gdb)
1: (5959) 1008: elapsed time 5056
1: (6005) Send Event AD7MessageEvent
ERROR: Unable to start debugging. Unexpected LLDB output from command "-exec-run". process exited with status -1 (attach failed ((os/kern) invalid argument))
1: (6018) <--gdb-exit
1: (6019) ->^exit
1: (6019) ->=thread-group-exited,id="i1"
1: (6019) ->(gdb)
1: (6022) <-logout
1: (6043) Send Event AD7ProgramDestroyEvent
The program '/Users/torsi/vsc-workspace/Helloworld' has exited with code 42 (0x0000002a).
How do I set the entitlements? if this is the problem?
Thanks,
Tom
Visual Studio Code does not support native LLDB debugging on Apple M1 CPU as of today.
Source: https://github.com/microsoft/vscode-cpptools/issues/7035
I used to have a fully functional yarn installation, everything working fine with my corporate proxy. But after 5 weeks I left it rotting, all of a sudden it is not working anymore.
When I run a simple yarn install, it stays there for some 2 minutes, then dies. Its output:
yarn install v1.22.4
<--- Last few GCs --->
[1464:0000000000441F90] 104273 ms: Scavenge 1396.5 (1425.7) -> 1395.7 (1426.2) MB, 4.5 / 0.0 ms (average mu = 0.147, current mu = 0.083) allocation failure
[1464:0000000000441F90] 104362 ms: Scavenge 1396.9 (1426.2) -> 1396.2 (1427.2) MB, 5.5 / 0.0 ms (average mu = 0.147, current mu = 0.083) allocation failure
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 000000013F3FDD8A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506
2: 000000013F3D8886 node::MakeCallback+4534
3: 000000013F3D9200 node_module_register+2032
4: 000000013F6F30DE v8::internal::FatalProcessOutOfMemory+846
5: 000000013F6F300F v8::internal::FatalProcessOutOfMemory+639
6: 000000013F8D9804 v8::internal::Heap::MaxHeapGrowingFactor+9620
7: 000000013F8D07E6 v8::internal::ScavengeJob::operator=+24550
8: 000000013F8CEE3C v8::internal::ScavengeJob::operator=+17980
9: 000000013F8D4D87 v8::internal::Heap::CreateFillerObjectAt+1175
10: 000000013FC727D3 v8::internal::NativesCollection<0>::GetScriptsSource+547
11: 000000013F35FD92 v8::internal::StackGuard::ArchiveSpacePerThread+52242
12: 000000013F360453 v8::internal::StackGuard::ArchiveSpacePerThread+53971
13: 000000013F441614 uv_dlerror+2452
14: 000000013F4423E8 uv_run+232
15: 000000013F3DFE7E node::NewContext+1390
16: 000000013F3E048B node::NewIsolate+603
17: 000000013F3E08E7 node::Start+823
18: 000000013F28F3CC node::MultiIsolatePlatform::MultiIsolatePlatform+604
19: 000000013FED863C v8::internal::compiler::OperationTyper::ToBoolean+129516
20: 0000000077B6556D BaseThreadInitThunk+13
21: 0000000077CC372D RtlUserThreadStart+29
After a while I found the culprit: at .yarnrc I had an invalid cache-folder setting:
cache-folder "L:\\yarn-cache"
So how can it be it used to work, but doesn't anymore?
When my corporation was setting up for social isolation, I decided to collect all the dependencies of all my active (and not so-active) projects in a pendrive, at the time at L:.
Now I'm accessing the desktop remotely, and the pendrive is not physically there.
I just wish that yarn could fail with a better message error.
Geeting an error while using mirror in hardops. I am using mac and it is working fine in windows. can it not be used in Mac?
Traceback (most recent call last):
File "///Library/Application Support/Blender/2.82/scripts/addons/HOps/operators/Gizmos/mirror.py", line 347, in invoke
current_tool = ToolSelectPanelHelper._tool_get_active(context, 'VIEW_3D', None)[0][0]
File "/Applications/Blender.app/Contents/Resources/2.82/scripts/startup/bl_ui/space_toolsystem_common.py", line 250, in _tool_get_active
for item in ToolSelectPanelHelper._tools_flatten(cls.tools_from_context(context, mode)):
AttributeError: type object 'ToolSelectPanelHelper' has no attribute 'tools_from_context'
location: :-1
Maybe it can help: I had this error on windows with previous currium Hard Ops, which is solved with latest Hard Ops update : Neodymium
Link to Hard Ops on BlenderMarket
Traceback (most recent call last):
File "tornado_runner.py", line 18, in <module>
main()
File "tornado_runner.py", line 15, in main
IOLoop.instance().start()
File "C:\Python27\lib\site-packages\tornado\ioloop.py", line 858, in start
event_pairs = self._impl.poll(poll_timeout)
File "C:\Python27\lib\site-packages\tornado\platform\select.py", line 63, in poll
self.read_fds, self.write_fds, self.error_fds, timeout)
select.error: (10038, 'An operation was attempted on something that is not a socket
it looks like the issue was solved for a while now, https://github.com/tornadoweb/tornado/issues/1360
But for last few days i started to see a lot of such errors in production windows environment. Does anyone have a clue?
I got the same issue with yours, and I searched it everywhere but can't find any solution in code layer.
Finally, I tried to reset winsock in my Windows, by running "netsh winsock reset" in command line, and it works.
the following problem is beyond my knowledge:
On my Windows machine I'm trying to uninstall the application.
Uninstaller reported that I need to close TotalCommander before continuing.
The application I want to uninstall has nothing to do with TotalCommander.
The only thing that connects my application and TotalCmmander is the library named msvcp120.dll that is used by both my aplication and TotalComader.
The difference is that TotalCommander uses the msvcp120.dll located in system directory (c:\Windows\Wystem32\msvcp120.dll) and my application uses library with the same name in completely different directory (c:\Users\john\AppData\Local\Ares\TestApp\msvcp120.dll). I have checked this in ProcessExplorer.
I've checked both TotalCommander and my application - both of them really load the library from different locations.
In my installer (I'm using Wix) I tried to disable InstallValidate action, but have ran into additional problems.
What I want to try now is to find out why am I being asked to close TotalComander when it has no obvious connection with the aplication I want to uninstall.
The following is the part of msi log file:
MSI (s) (C0:3C) [09:46:22:634]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1603
Info 1603.The file C:\Users\john\AppData\Local\Ares\TestApp\msvcp120.dll is being held in use by the following process: Name: explorer, Id: 4032, Window Title: '(not determined yet)'. Close that application and retry.
MSI (s) (C0:3C) [09:46:22:635]: Note: 1: 2205 2: 3: Error
MSI (s) (C0:3C) [09:46:22:635]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1603
Info 1603.The file C:\Users\john\AppData\Local\Ares\TestApp\msvcp120.dll is being held in use by the following process: Name: TOTALCMD64, Id: 11352, Window Title: '(not determined yet)'. Close that application and retry.
MSI (s) (C0:3C) [09:46:22:635]: Note: 1: 2205 2: 3: Error
MSI (s) (C0:3C) [09:46:22:635]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1603
Info 1603.The file C:\Users\john\AppData\Local\Ares\TestApp\msvcp120.dll is being held in use by the following process: Name: TestApp, Id: 12056, Window Title: '(not determined yet)'. Close that application and retry.
Here I can see that the C:\Users\john\AppData\Local\Ares\TestApp\msvcp120.dll library is reported as being held by explorer, TotalCommander and my TestApp, but I'm asked to close only TotalCommander.
Thanks for any answer.