Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-14959

Log more debug data on "Access on reserved section?" case

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Minor
    • None
    • NTCore
    • None

    Description

      If that applies, add some detailed debug log and/or an (temporary) ASSERT(), to get a backtrace, to help figure out the following code case.
      If not, how can this case be investigated? Only with a debugger?

      https://git.reactos.org/?p=reactos.git;a=blob;f=ntoskrnl/mm/ARM3/pagfault.c;hb=e7d2bbe726f605d0a0c69f3e2add6ee84bba8124#l1122

      1079 MiResolveProtoPteFault(IN BOOLEAN StoreInstruction,
      ...
      1123     /* Make sure there's some protection mask */
      1124     if (TempPte.u.Long == 0)
      1125     {
      1126         /* Release the lock */
      1127         DPRINT1("Access on reserved section?\n");
      1128         MiReleasePfnLock(OldIrql);
      1129         return STATUS_ACCESS_VIOLATION;
      1130     }
      

      Moved from CORE-14938,
      with at least yet unresolved CORE-14599.

      https://jira.reactos.org/browse/CORE-14959?jql=text%20~%20%22Access%20on%20reserved%20section%22%20and%20resolution%20is%20not%20EMPTY
      5 resolved.
      https://jira.reactos.org/browse/CORE-14959?jql=text%20~%20%22Access%20on%20reserved%20section%22%20and%20resolution%20is%20EMPTY
      9 open.

      Attachments

        Activity

          People

            bug zilla Bug Zilla
            Serge Gautherie Serge Gautherie
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: