[reactos] 01/09: [CRT_APITEST] Restore direction flag to avoid false RTC break

[Timo Kreuzer]

https://git.reactos.org/?p=reactos.git;a=commitdiff;h=f71940efb17014a4cb7e5…

commit f71940efb17014a4cb7e5c112cf7e7ae5a5f7011
Author:     Timo Kreuzer <timo.kreuzer(a)reactos.org>
AuthorDate: Mon Aug 8 10:33:02 2022 +0300
Commit:     Timo Kreuzer <timo.kreuzer(a)reactos.org>
CommitDate: Thu Dec 1 20:17:40 2022 +0200

    [CRT_APITEST] Restore direction flag to avoid false RTC break
    
    With set direction flag the variables will not be initialized properly.
---
 modules/rostests/apitests/crt/strlen.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/rostests/apitests/crt/strlen.c
b/modules/rostests/apitests/crt/strlen.c
index 182dcf68ccf..7f0c9d7e6fe 100644
--- a/modules/rostests/apitests/crt/strlen.c
+++ b/modules/rostests/apitests/crt/strlen.c
@@ -48,8 +48,8 @@ Test_strlen(PFN_STRLEN pstrlen)
     eflags = __readeflags();
     __writeeflags(eflags | EFLAGS_DF);
     len = pstrlen(teststr + 4);
-    eflags = __readeflags();
-    ok((eflags & EFLAGS_DF) != 0, "Direction flag in ELFAGS was
changed.");
+    ok((__readeflags() & EFLAGS_DF) != 0, "Direction flag in ELFAGS was
changed.");
+    __writeeflags(eflags);
 
     /* Only test this for the exported versions, intrinsics might do it
        differently. It's up to us to not do fishy stuff! Also crtdll does