Ignore:
Timestamp:
Oct 1, 2002, 1:37:19 PM (23 years ago)
Author:
sandervl
Message:

Be careful with stack usage in exception handler during XCPT_GUARD_PAGE_VIOLATION

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/kernel32/exceptions.cpp

    r8920 r9315  
    1 /* $Id: exceptions.cpp,v 1.65 2002-07-26 10:47:33 sandervl Exp $ */
     1/* $Id: exceptions.cpp,v 1.66 2002-10-01 11:37:19 sandervl Exp $ */
    22
    33/*
     
    11371137    int prevlock = LogException(ENTER_EXCEPTION);
    11381138
    1139     //print exception name & exception type
    1140     sprintfException(pERepRec, pERegRec, pCtxRec, p, szTrapDump);
     1139    //Print exception name & exception type
     1140    //Not for a guard page exception as sprintfException uses a lot of stack
     1141    //and can trigger nested guard page exceptions (crash)
     1142    if(pERepRec->ExceptionNum != XCPT_GUARD_PAGE_VIOLATION) {
     1143        sprintfException(pERepRec, pERegRec, pCtxRec, p, szTrapDump);
     1144    }
    11411145
    11421146    /* Access violation at a known location */
Note: See TracChangeset for help on using the changeset viewer.