[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: SEH logging
From:       Francois Gouget <fgouget () free ! fr>
Date:       2001-04-17 18:33:37
[Download RAW message or body]

On 17 Apr 2001, Alexandre Julliard wrote:

> Francois Gouget <fgouget@free.fr> writes:
> 
> >    In this implementation exception.c reuses format_exception_msg()
> > which is normally used to display the dialog box asking whether to debug
> > the exception or not. Since this is all in ntdll it works.
> 
> Actually win32/except.c is part of kernel, it's only linked in ntdll
> now because separation is not finished. So you cannot call
> format_exception_msg from ntdll.

   Ah, ok. That's annoying indeed.


> And anyway this would print
> "unhandled xxx" for all exceptions, which is misleading since they
> might be handled later on.

   That would have been easy to fix.


> Also I don't think the core exception routines should know about
> specific exception codes like EXCEPTION_WINE_STUB. If you want a
> message on stubs, it should be done in the .spec.c file before the
> call to RtlRaiseException.

   Ok. Actually what I was striving for was to get a message that
describes the exception in more detail than the current 'code=c0000005
flags=0', independently of which exception occurs.


--
Francois Gouget         fgouget@free.fr        http://fgouget.free.fr/
     The software said it requires Win95 or better, so I installed Linux.

[prev in list] [next in list] [prev in thread] [next in thread]