Uploaded image for project: 'ReactOS Test Suite'
  1. ReactOS Test Suite
  2. ROSTESTS-135

ntdll:RtlDosSearchPath_U 3 failures

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 0.4.5
    • Component/s: ReactOS Tests
    • Labels:
      None

      Description

      See for example http://www.reactos.org/sites/all/modules/reactos/testman/detail.php?id=14843072&prev=0 :

      RtlDosSearchPath_U.c:266: Test failed: CheckBuffer failed
      RtlDosSearchPath_U.c:267: Test failed: Length = 110
      RtlDosSearchPath_U.c:268: Test failed: PartName = 00000000 ((null)), expected 55555555
      RtlDosSearchPath_U: 297 tests executed (0 marked as todo, 3 failures), 0 skipped.

      This test fails with exactly the same errors when using either our ntdll.dll or Windows 2k3 SP1 (or 2) ntdll.dll.

      1- All the other Rtl*Path* tests work --> APIs seem to work.
      2- For this API: failure in value of Length and FileName (expected: 0, NULL ; measured !=0, != NULL)
      3- Putting Windows' ntdll.dll instead of ReactOS' ntdll.dll: very same failure.
      4- Code path analysis: Call to RtlDoesFileExists_UEx, then (in case of success) to RtlGetFullPathName_U (and co.)
         ----> let's test RtlDoesFileExists_UEx with the computed values (TODO)
         ----> On Windows: should fail (TODO / CHECK)
         ----> On ReactOS: succeeds (TODO / RECHECK)
       
         Therefore, can only be a problem caused sowhere else than in ntdll --> Suppose our ntdll code is also working.
         Then:
         RtlDoesFileExists_UEx --> RtlDoesFileExists_UstrEx --> RtlDosPathNameToRelativeNtPathName_Ustr (at the moment, only APIs that put in form the different path elements).
                                                                              |
                                                                              |
                                                                              V
                                                      ZwQueryAttributesFile(&ObjectAttributes, &BasicInformation);
       
      It would be interesting to check the return value of the ZwQueryAttributesFile call (should be the same in ReactOS and in Windows-on-ROS a priori).
          --> Broken return value --> Problem of file-system (or worse, in the kernel??)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ThFabba ThFabba
                Reporter:
                hbelusca hbelusca
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: