- 23.04.2025 1 коммит
-
-
Whindmar Saksit создалNote: A bug in the classic button prevents it from sending CDDS_POSTPAINT if the button has no text, the button resource has a space in its text as a workaround.
-
- 22.04.2025 4 коммита
-
-
Whindmar Saksit создал
-
Marcin Jabłoński создал
-
-
Whindmar Saksit создал
-
- 21.04.2025 1 коммит
-
-
- 20.04.2025 1 коммит
-
-
Hermès Bélusca-Maïto создал
Since the setuplib.dll isn't available after installing ReactOS, build instead a static library that is then used for the dll, and linked into the setuplib_unittest, so that it can be run in our test-suite. Addendum to commit d7c1d220.
-
- 19.04.2025 7 коммитов
-
-
Eric Kohl создал
This header is not to be used outside of dhcpcsvc because it contains the data structures for the communication between the client and the server part within dhcpcsvc. That is why it is moved inside of dhcpcsvc and renamed to rosdhcp_pipe.h.
-
Hermès Bélusca-Maïto создал
CORE-20107 Improve the minimal handling done in the fall-back KdSend/ReceivePacket() routines when they are invoked by KD64 (in Release build). Part of my `kdbg_tests_kdio_split` branch for splitting kd/kdio.c into a separate KD dll. KdSendPacket: - Silently ignore PACKET_TYPE_KD_STATE_CHANGE32/64 DbgKdLoadSymbolsStateChange notification. - Partially manage and log the unhandled PACKET_TYPE_KD_STATE_CHANGE DbgKdExceptionStateChange notification. - Log other unhandled PACKET_TYPE_KD_STATE_CHANGE32/64 and PACKET_TYPE_KD_STATE_MANIPULATE notifications. When KdSendPacket receives the DbgKdExceptionStateChange notification, it cannot handle it (no debugger is there!). However, we need to claim the debugger to be present, so that its KD64 caller: KdpSendWaitContinue(), can call back KdReceivePacket(PACKET_TYPE_KD_STATE_MANIPULATE), which, in turn, informs KD that the exception cannot be handled, by returning a failure code in the ManipulateState's ContinueStatus. During bugchecks, this allows KiBugCheckDebugBreak() to not loop infinitely, but instead fall back into calling HalHaltSystem() to halt the computer.
-
Serge Gautherie создал
When KDBG isn't included in the kernel (Release build), the fall-back KdSend/ReceivePacket() routines are invoked by KD64. A minimal handling of the basic packets needs to be done: PACKET_TYPE_KD_STATE_CHANGE32/64 for KdSendPacket(), and PACKET_TYPE_KD_POLL_BREAKIN, PACKET_TYPE_KD_STATE_MANIPULATE for KdReceivePacket(). Addendum to commit 2046a17e CORE-20107
-
Hermès Bélusca-Maïto создал
RtlpBreakWithStatusInstruction is just a label for KD. On machines that have register calling conventions (basically all except x86), the `Status` parameter for `DbgBreakPointWithStatus` is stored in the first argument register. https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-dbgbreakpointwithstatus On the x64 platform, `DbgBreakPointWithStatus` only uses the ECX register and leaves EAX untouched. Verified on Windows.
-
Hermès Bélusca-Maïto создал
This helper was introduced in commit b041530f (r8551), and its last remaining usage removed in commit f038f4a8 (r23636).
-
-
Eric Kohl создал
-
- 18.04.2025 23 коммита
-
-
Eric Kohl создал
-
-
-
-
Whindmar Saksit создал
Implements a couple of extra commands in IShellBrowser and adds support for the AppKeys fallback registry key (used when the foreground application does not handle the command).
-
Timo Kreuzer создал
-
Timo Kreuzer создал
-
Timo Kreuzer создал
-
Timo Kreuzer создал
-
Timo Kreuzer создал
-
-
Timo Kreuzer создал
-
Timo Kreuzer создал
-
Timo Kreuzer создал
They were introduced when MEMROY_AREAs and VAD still lived in different tables to synchronize between them. Since some time MEMORY_AREAs are special VADs and live in the same table as ARM³ VADs, but with flags to distinguish them. Since then the only reason that the fake MEMORY_AREAs still existed was to determine whether a VAD that is a MEMORY_AREA is still handled by ARM³ (which is the case for some kernel VADs, like for paged pool). This is no longer required as it is now determined by a 2nd flag in the VAD itself. Additionally, we tried to insert the fake MEMORY_AREAs into the VAD table, which would fail, because it was already occupied by the ARM³ VAD, but the failure was ignored.
-
-
Timo Kreuzer создал
- Implement MiLocateVad and make MiLocateAddress call it - Use MiLocateVad in MmAccessFault to get the VAD - Check VadFlags for whether this is an ARM³ VAD/MEMORY_AREA
-
Timo Kreuzer создал
-
Timo Kreuzer создал
This is to distinguish them from ARM³ memory areas, which we use for some kernel regions, like paged pool.
-
Timo Kreuzer создал
-
Timo Kreuzer создал
Use this instead of MmLocateMemoryAreaByRegion to determine whether we can inert a section at the requested base address. This will be required to get rid of fake memory areas allocated for each ARM³ VAD.
-
Timo Kreuzer создал
In MmCleanProcessAddressSpace we already delete VADs that are RosMm memory areas by calling MiRosCleanupMemoryArea, so we never reach the later check. This code path is from a time when VADs and memory areas lived in different tables, which is no longer the case.
-
-
Timo Kreuzer создал
-
- 17.04.2025 3 коммита
-
-
Katayama Hirofumi MZ создал
Related to #7870. IMM32 uses NDK. So, we have to remove Wine dependency. JIRA issue: CORE-5743 - Add dll/win32/imm32/debug.h. - Remove Wine dependency. - Update the documentation (media/doc/WINESYNC.txt).
-
Adam Słaboń создал
- Fix the crash due to copying the memory to wrong destination buffer. - Fix the check for trailing backlash on path string.
-
Adam Słaboń создал
- `MountMgrVolumeMountPointChanged()`: Set status code in all failure paths and correct the check for remote or removable media. - `DeleteRemoteDatabaseEntry()`: Do not allow the database with size of zero. - `QueryVolumeName()`: Use reparse point file reference when no file name is supplied.
-