Okay, my bad. The exception handler was getting
called, ergo the dialog box telling me it crashed.
Sorry for the noise.
--Juan
--- Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Juan Lang <[EMAIL PROTECTED]> writes:
>
> > Interesting. The behavior of the program that
> called
> > it (ipconfi
Well, you could try a +snoop,+relay,+seh,+tid trace. If snoop causes it
to crash then drop that one, relay is normally enough.
On Sat, 2003-09-06 at 08:38, Juan Lang wrote:
> --- Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> > Could you try
> > reverting the FormatMessage fix and check why the
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Juan Lang
> Sent: 05 September 2003 23:28
> To: Alexandre Julliard
> Cc: [EMAIL PROTECTED]
> Subject: Re: Resend: ntdll loader fix
>
>
> Interesting. The behavior o
--- Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Could you try
> reverting the FormatMessage fix and check why the
> exception handler
> doesn't do its job?
I can. How can I investigate the exception handler?
>From memory, here's what I observed:
With the FormatMessage fix, of course, everyt
Interesting. The behavior of the program that called
it (ipconfig.exe) was different, it crashed in a
different location. But since the FormatMessage fix
got rid of the crash altogether, I'm not particularly
concerned.
Thanks,
--Juan
--- Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> Juan Lang
Juan Lang <[EMAIL PROTECTED]> writes:
> Interesting. The behavior of the program that called
> it (ipconfig.exe) was different, it crashed in a
> different location. But since the FormatMessage fix
> got rid of the crash altogether, I'm not particularly
> concerned.
Well I am, the behavior shou
Juan Lang <[EMAIL PROTECTED]> writes:
> ChangeLog: fixes RtlImageNtHeader when hModule is
> NULL.
>
> One line patch (two tokens!), should be easy enough to
> verify correctness.
Well, it may be correct, but it's useless, there's already an
exception handler that deals with that.
--
Alexandre J
