Index
> Windows > Exception |
| Author |
|
|
Galkov 28 Aug 2005, 19:54
How may I catch this in Fasm
FPU, for example..... _________________ sorry for my bad english  |
|||
28 Aug 2005, 19:54 |
|
|
Reverend 28 Aug 2005, 22:24
Under windows:
Code: set_exception_handler: push handler push dword [fs:0] mov [fs:0], esp ; some code goes here ; ... remove_exception_handler: pop dword [fs:0] add esp, 4 ; ... handler: ; what happens when an excepiton occured ; ... |
|||
|
28 Aug 2005, 22:24 |
|
|
comrade 29 Aug 2005, 02:28
you can check SEH example on mywebsite
http://comrade.win32asm.com/ its all the way down in the Sources page |
|||
|
29 Aug 2005, 02:28 |
|
|
Galkov 29 Aug 2005, 06:04
Reverend, and is it enough for catch
((sorry - that is question of beginer)) comrade, what project on yourweb you are advised for checking  |
|||
|
29 Aug 2005, 06:04 |
|
|
revolution 29 Aug 2005, 07:04
Quote: and is it enough for catch? In the "handler" code you would normally check the exception code and depending on what happened then set a new EIP in the CONTEXT record before RETurning. |
|||
|
29 Aug 2005, 07:04 |
|
|
Galkov 29 Aug 2005, 19:13
Tanks for ALL
Begining of understanding are coming for me 
I'll try to translate SEH-example of comrade to Fasm ((Oh, I find it - it was latest of webpage)) Nevertheless, there are no definition of structures EXCEPTION_RECORD and CONTEXT in Fasm.... ========================== One question more: comrade, in your example esp is saving in a global variable seh. Is [FS:0] already failed in ErrorHandler _________________ sorry for my bad english |
|||
|
29 Aug 2005, 19:13 |
|
|
revolution 30 Aug 2005, 01:23
Quote: there are no definition of structures EXCEPTION_RECORD and CONTEXT in Fasm Code: SIZE_OF_80387_REGISTERS = 80 EXCEPTION_ACCESS_VIOLATION = 0C0000005h EXCEPTION_DATATYPE_MISALIGNMENT = 080000002h EXCEPTION_BREAKPOINT = 080000003h EXCEPTION_SINGLE_STEP = 080000004h EXCEPTION_ARRAY_BOUNDS_EXCEEDED = 0C000008Ch EXCEPTION_FLT_DENORMAL_OPERAND = 0C000008Dh EXCEPTION_FLT_DIVIDE_BY_ZERO = 0C000008Eh EXCEPTION_FLT_INEXACT_RESULT = 0C000008Fh EXCEPTION_FLT_INVALID_OPERATION = 0C0000090h EXCEPTION_FLT_OVERFLOW = 0C0000091h EXCEPTION_FLT_STACK_CHECK = 0C0000092h EXCEPTION_FLT_UNDERFLOW = 0C0000093h EXCEPTION_INT_DIVIDE_BY_ZERO = 0C0000094h EXCEPTION_INT_OVERFLOW = 0C0000095h EXCEPTION_PRIV_INSTRUCTION = 0C0000096h EXCEPTION_IN_PAGE_ERROR = 0C0000006h EXCEPTION_ILLEGAL_INSTRUCTION = 0C000001Dh EXCEPTION_NONCONTINUABLE_EXCEPTION = 0C0000025h EXCEPTION_STACK_OVERFLOW = 0C00000FDh EXCEPTION_INVALID_DISPOSITION = 0C0000026h EXCEPTION_GUARD_PAGE = 0C0000001h CONTROL_C_EXIT = 0C000013Ah EXCEPTION_MAXIMUM_PARAMETERS = 15 EXCEPTION_EXECUTE_HANDLER = 1 EXCEPTION_CONTINUE_SEARCH = 0 EXCEPTION_CONTINUE_EXECUTION = -1 struc EXCEPTION_POINTERS { .ExceptionRecord dd ? .ContextRecord dd ? } struct EXCEPTION_POINTERS struc EXCEPTION_RECORD { .ExceptionCode dd ? .ExceptionFlags dd ? .ExceptionRecord dd ? .ExceptionAddress dd ? .NumberParameters dd ? .ExceptionInformation rd EXCEPTION_MAXIMUM_PARAMETERS } struct EXCEPTION_RECORD struc CONTEXT { .ContextFlags dd ? ;context flags .Dr0 dd ? ;debug register #0 .Dr1 dd ? ;debug register #1 .Dr2 dd ? ;debug register #2 .Dr3 dd ? ;debug register #3 .Dr6 dd ? ;debug register #6 .Dr7 dd ? ;debug register #7 .ControlWord dd ? ;fpu context .StatusWord dd ? .TagWord dd ? .ErrorOffset dd ? .ErrorSelector dd ? .DataOffset dd ? .DataSelector dd ? .RegisterArea rb SIZE_OF_80387_REGISTERS .Cr0NpxState dd ? .SegGs dd ? ;gs register .SegFs dd ? ;fs register .SegEs dd ? ;es register .SegDs dd ? ;ds register .Edi dd ? ;edi register .Esi dd ? ;esi register .Ebx dd ? ;ebx register .Edx dd ? ;edx register .Ecx dd ? ;ecx register .Eax dd ? ;eax register .Ebp dd ? ;ebp register .Eip dd ? ;eip register .SegCs dd ? ;cs register .EFlags dd ? ;eflags register .Esp dd ? ;esp register .SegSs dd ? ;ss register } struct CONTEXT |
|||
|
30 Aug 2005, 01:23 |
|
|
Galkov 30 Aug 2005, 04:18
excellent
 |
|||
|
30 Aug 2005, 04:18 |
|
|
comrade 30 Aug 2005, 16:17
this also might be useful:
Code: XCPTLU xcptExceptionCodes[] = { {EXCEPTION_ACCESS_VIOLATION, "EXCEPTION_ACCESS_VIOLATION"}, {EXCEPTION_ARRAY_BOUNDS_EXCEEDED, "EXCEPTION_ARRAY_BOUNDS_EXCEEDED"}, {EXCEPTION_BREAKPOINT, "EXCEPTION_BREAKPOINT"}, {EXCEPTION_DATATYPE_MISALIGNMENT, "EXCEPTION_DATATYPE_MISALIGNMENT"}, {EXCEPTION_FLT_DENORMAL_OPERAND, "EXCEPTION_FLT_DENORMAL_OPERAND"}, {EXCEPTION_FLT_DIVIDE_BY_ZERO, "EXCEPTION_FLT_DIVIDE_BY_ZERO"}, {EXCEPTION_FLT_INEXACT_RESULT, "EXCEPTION_FLT_INEXACT_RESULT"}, {EXCEPTION_FLT_INVALID_OPERATION, "EXCEPTION_FLT_INVALID_OPERATION"}, {EXCEPTION_FLT_OVERFLOW, "EXCEPTION_FLT_OVERFLOW"}, {EXCEPTION_FLT_STACK_CHECK, "EXCEPTION_FLT_STACK_CHECK"}, {EXCEPTION_FLT_UNDERFLOW, "EXCEPTION_FLT_UNDERFLOW"}, {EXCEPTION_ILLEGAL_INSTRUCTION, "EXCEPTION_ILLEGAL_INSTRUCTION"}, {EXCEPTION_IN_PAGE_ERROR, "EXCEPTION_IN_PAGE_ERROR"}, {EXCEPTION_INT_DIVIDE_BY_ZERO, "EXCEPTION_INT_DIVIDE_BY_ZERO"}, {EXCEPTION_INT_OVERFLOW, "EXCEPTION_INT_OVERFLOW"}, {EXCEPTION_INVALID_DISPOSITION, "EXCEPTION_INVALID_DISPOSITION"}, {EXCEPTION_NONCONTINUABLE_EXCEPTION, "EXCEPTION_NONCONTINUABLE_EXCEPTION"}, {EXCEPTION_PRIV_INSTRUCTION, "EXCEPTION_PRIV_INSTRUCTION"}, {EXCEPTION_SINGLE_STEP, "EXCEPTION_SINGLE_STEP"}, {EXCEPTION_STACK_OVERFLOW, "EXCEPTION_STACK_OVERFLOW"}, { 0, 0 } }; //########################################################################### XCPTLU xcptExceptionDescriptions[] = { {EXCEPTION_ACCESS_VIOLATION, "The thread tried to read from or write to a virtual address for which it does not have the appropriate access."}, {EXCEPTION_ARRAY_BOUNDS_EXCEEDED, "The thread tried to access an array element that is out of bounds and the underlying hardware supports bounds checking."}, {EXCEPTION_BREAKPOINT, "A breakpoint was encountered."}, {EXCEPTION_DATATYPE_MISALIGNMENT, "The thread tried to read or write data that is misaligned on hardware that does not provide alignment. For example, 16-bit values must be aligned on 2-byte boundaries; 32-bit values on 4-byte boundaries, and so on."}, {EXCEPTION_FLT_DENORMAL_OPERAND, "One of the operands in a floating-point operation is denormal. A denormal value is one that is too small to represent as a standard floating-point value."}, {EXCEPTION_FLT_DIVIDE_BY_ZERO, "The thread tried to divide a floating-point value by a floating-point divisor of zero."}, {EXCEPTION_FLT_INEXACT_RESULT, "The result of a floating-point operation cannot be represented exactly as a decimal fraction."}, {EXCEPTION_FLT_INVALID_OPERATION, "This exception represents any floating-point exception not included in this list."}, {EXCEPTION_FLT_OVERFLOW, "The exponent of a floating-point operation is greater than the magnitude allowed by the corresponding type."}, {EXCEPTION_FLT_STACK_CHECK, "The stack overflowed or underflowed as the result of a floating-point operation."}, {EXCEPTION_FLT_UNDERFLOW, "The exponent of a floating-point operation is less than the magnitude allowed by the corresponding type."}, {EXCEPTION_ILLEGAL_INSTRUCTION, "The thread tried to execute an invalid instruction."}, {EXCEPTION_IN_PAGE_ERROR, "The thread tried to access a page that was not present, and the system was unable to load the page. For example, this exception might occur if a network connection is lost while running a program over the network."}, {EXCEPTION_INT_DIVIDE_BY_ZERO, "The thread tried to divide an integer value by an integer divisor of zero."}, {EXCEPTION_INT_OVERFLOW, "The result of an integer operation caused a carry out of the most significant bit of the result."}, {EXCEPTION_INVALID_DISPOSITION, "An exception handler returned an invalid disposition to the exception dispatcher. Programmers using a high-level language such as C should never encounter this exception."}, {EXCEPTION_NONCONTINUABLE_EXCEPTION, "The thread tried to continue execution after a noncontinuable exception occurred."}, {EXCEPTION_PRIV_INSTRUCTION, "The thread tried to execute an instruction whose operation is not allowed in the current machine mode."}, {EXCEPTION_SINGLE_STEP, "A trace trap or other single-instruction mechanism signaled that one instruction has been executed."}, {EXCEPTION_STACK_OVERFLOW, "The thread used up its stack."}, { 0, 0 } }; |
|||
|
30 Aug 2005, 16:17 |
|
|
Galkov 30 Aug 2005, 19:01
undoubtedly
 |
|||
|
30 Aug 2005, 19:01 |
|
< Last Thread | Next Thread > |
Forum Rules:
|