3 May
2006
3 May
'06
1:53 p.m.
hey, it's not like we didn't pressure them all
the time. And to repeat
myself, we need this in C. Not C++. Absolutely sure of it. And we'll
need it to catch faults, such as memory access violations, not just
program exceptions - in fact, that's what using SEH in the kernel is all
about
Can someone explain to me why someone doesnt just go and bgab the MingW/GCC
source code and write a proper SEH implementation that is source-level and
binary-level compatible with the MS implementation (i.e. it uses the same
source syntax as the MS implementation and the same OS functionality and
mechanisim as the MS implementation)
I have seen several "under the hood" documents explaining exactly how SEH
works at the OS level (I even have code that for various reasons I wont go
into needs to walk the exception handler list and remove a particular
handler from the list in order to make something work right) so its not
like its undocumented or a black art (unlike many of the pieces of windows
ReactOS needs to implement and be compatible with)