--- Alexandre Julliard julliard@winehq.com 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, everything is hunky dory. If you have a copy of win9x's route.exe, try "wine -- route.exe print"
Without it and with this fix, ipconfig.exe crashes in msvcrt.printf, presumably from a NULL format string. (I hacked FormatMessage to return "bogus" rather than NULL, and ipconfig.exe printed bogus and exited.)
Without either fix, I get a seg fault. If I run it in winedbg, I can't break, but it tells me there's a page fault. If I run it in gdb, I get a page fault.
How can I investigate further?
I'm running on a weird beta of RH8.1 (never released?), configured --with-nptl.
--Juan
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com