[fpc-pascal]TRY EXCEPT Bug

Pierre Muller pierre at idefix.wisa.be
Tue Oct 3 01:10:22 CEST 2000


At 18:42 02/10/00 +0200, you wrote:
>>>My suggestion is to move the basic exception stuff by default into the
>>>system unit and remove the dpmiexcp unit.
>>>
>>>Btw, I am currently working on updating the 'fully working exception
>>>handling' :] to allow catching of the missing hardware exceptions. I've
>>>stumbled upon the following remark in excptn.as:
>>>
>>>/* ;WARNING WARNING WARNING
>>>   ;The mechanism for passing signals between the debugger
>>>   ;and the debuggee relies on the *exact* instructions between
>>>   ;EXCEPTION_ENTRY($13) above and "cmpb $0, forced" instruction
>>>   ;below!  These instructions are stored in forced_test[] buffer
>>>   ;in src/debug/common/dbgcom.c.  Do NOT change anything between
>>>   ;these two instructions, or you will break signal support in
>>>   ;the debuggers!!  */
>>>
>>>Well, the problem is that to support those there is (well, I think so)
>>>_need_ of breaking this warning. My question is whether this still applies
>?
>>>Because this would either mean that the go32v2 target won't get that
>support
>>>anymore or breaking debugging support of all these programs....
>>I strongly object to this!!!!!!!!!!!!!!!!!!!!!!!!
>>
>> This will break signal support for GDB and a spent a lot of time to
>>getting this to work !!!
>
>That's why I was asking.
>
>>  Why do you need to change this anyway ??
>
>To add hardware exception #18 and #19 introduced by Pentium(!!!!)/PIII+
>processors.


 Then we should add them before :

  EXCEPTION_ENTRY $18
  EXCEPTION_ENTRY $19
  EXCEPTION_ENTRY $0

  this will require some changes in the 
djgpp_exception_setup function
but its not that difficult !





More information about the fpc-pascal mailing list