July 2002 - Wine-Devel - list.winehq.org

Re: warcraft 3

by leanne

Matthieu Foillard wrote: > i finally made warcraft III working : > > 1. rename the Movies folder as Jesse Allen did. > 2. get winex from cvs, then patch srcs with > http://www.winehq.com/hypermail/wine-patches/2002/06/0041.html > 3. configure wine using ./configure --enable-opengl ..., then build it. > 4. run warcraft using : wine /path/War3.exe ( the -opengl doesn't work > for me) > 5. enjoy ! > I followed your procedures, X crashed when I started to run it. It said ".... deadlock ..." Any idea? Thanks. Leanne

July 18, 2002

Re: Bug in WINPOS_GetWinOffset? (was Possible Fix?)

by Tony Lambregts

Joshua Thielen wrote: >Hello everybody, > >I don't know if this is related to the bug Anthony >encountered, but why does WINPOS_GetWinOffset() use a >goto when it adds the offset of a parent window from >another process? Shouldn't the server request >'get_window_parents' be used to retrieve all of the >parent windows from other processes? Or can there only >be one parent from another process? > >Josh > >__________________________________________________ >Do You Yahoo!? >Yahoo! Autos - Get free new car price quotes >http://autos.yahoo.com > > > > Looks like we have the makings of a good bug report here. Could one of you start a bug report in bugzilla. (maybe not so) ugly hack included Tony Lambregts

July 18, 2002

Re: OLE classes registration

by Dmitry Timoshkov

"John K. Hohm" <jhohm(a)acm.org> wrote: > This reminds me that a self-registerable dll is supposed to have a > VS_VERSION_INFO resource, with an empty "OLESelfRegister" value in > the "StringFileInfo" block. comcat.dll has no resources; is there a standard > Wine way to add such version info? Please have a look at include/wine/wine_common_ver.rc and a couple of version resources using it, for instance dlls/kernel/version.rc and dlls/kernel/version16.rc. Also do not forget to add RC_SRCS to Makefile.in in the case there is no resources at all yet, or just include new version.rc into an existing .rc file. -- Dmitry.

July 18, 2002

Re: Virtual Pages difference - Spotted with VirtualQuery()

by Tony Lambregts

Max wrote: >As usual, AutoCAD seems to be a good test-bench for wine :-) >I spotted the problem that seemed coming from VirtualQuety function, but >that is (I guess... hmmmm) more a problem of memory handling in wine. > >I made a little test app; here the results in wine and win2k, later on >the app itself : > >WINE RESULTS : > >Memory info about '004012F0' : > Base Address : 00401000 > Allocation Base : 00400000 > Allocation Protect : PAGE_READONLY | PAGE_WRITECOPY | > PAGE_EXECUTE_READWRITE | PAGE_NOACCESS > Region Size : 00017000 > State : MEM_COMMIT > Protect : PAGE_WRITECOPY <----- HERE > Type : MEM_PRIVATE > >WIN2k RESULTS : > >Memory info about '004012F0' : > Base Address : 00401000 > Allocation Base : 00400000 > Allocation Protect : PAGE_EXECUTE_WRITECOPY > Region Size : 00001000 > State : MEM_COMMIT > Protect : PAGE_EXECUTE_READ <---- AND HERE > Type : MEM_IMAGE > >Well, dunno too much about Type field, I didn't find an app that check it yet; >I did find the app that uses Protect flag; I think it's poor coded, but as >usual we should make bad apps work too :-) >The app put some data in code page, not yet spotted if hard or soft-coded, >then before reading it checks Protect field to see if it has not set the >PAGE_GUARD, NO_ACCESS and WRITECOPY flags; if t has, it hangs some 10.000 >lines later (sigh....) >I think wine should set Protect flag quite as like as possible as windoze > >For AutoCAD2000 I put a dirty hack in process.c, but is really ugly; i'd >prefer not to put my hands (bytes ?) too deeply inside some code that I don't >understand completely... > >Attached is the test source (compiled in Borland CBuilder, but should work >with any compiler, apart some unuseful pragma's). >If needed I can post the compiled too :-) > >Regards > >Max > > This is an excellent bug report but even if someone starts working on it right away it would be nice to have this stuff in bugzilla. That includes the exe and your (maybe not-so) ugly hack. Tony Lambregts

July 18, 2002

Re: CxxFrameHandler problem

by Steven Edwards

> That's a start, yes, thanks. I'll need a more > complete example with > nested try blocks, destructors all over the place, > typed exceptions, > etc. to make sure I understand all the compiler > internal structures; > but I can at least try to make that simple case not > crash... Taken from MSDN (see fair use) here is the msdn example page. ------ The following example demonstrates C++ exception handling using classes with destructor semantics. It declares two C++ classes; one (class CTest) for defining the exception object itself, and the second (class CDtorDemo) for demonstrating the destruction of a separate frame object during stack unwinding: Example // exceptions_Exception_Examples.cpp // compile with: /EHsc #include <iostream> using namespace std; void MyFunc( void ); class CTest { public: CTest(){}; ~CTest(){}; const char *ShowReason() const { return "Exception in CTest class."; } }; class CDtorDemo { public: CDtorDemo(); ~CDtorDemo(); }; CDtorDemo::CDtorDemo() { cout << "Constructing CDtorDemo." << endl; } CDtorDemo::~CDtorDemo() { cout << "Destructing CDtorDemo." << endl; } void MyFunc() { CDtorDemo D; cout<< "In MyFunc(). Throwing CTest exception." << endl; throw CTest(); } int main() { cout << "In main." << endl; try { cout << "In try block, calling MyFunc()." << endl; MyFunc(); } catch( CTest E ) { cout << "In catch handler." << endl; cout << "Caught CTest exception type: "; cout << E.ShowReason() << endl; } catch( char *str ) { cout << "Caught some other exception: " << str << endl; } cout << "Back in main. Execution resumes here." << endl; return 0; } If a matching catch handler is found, and it catches by value, its formal parameter is initialized by copying the exception object. If it catches by reference, the parameter is initialized to refer to the exception object. After the formal parameter is initialized, the process of "unwinding the stack" begins. This involves the destruction of all automatic objects that were constructed (but not yet destructed) between the beginning of the try block associated with the catch handler and the exception's throw site. Destruction occurs in reverse order of construction. The catch handler is executed and the program resumes execution following the last handler (that is, the first statement or construct that is not a catch handler). Output In main. In try block, calling MyFunc(). Constructing CDtorDemo. In MyFunc(). Throwing CTest exception. Destructing CDtorDemo. In catch handler. Caught CTest exception type: Exception in CTest class. Back in main. Execution resumes here. Note the declaration of the exception parameter in both catch handlers: catch( CTest E ) { // ... } catch( char *str ) { // ... } You do not need to declare this parameter; in many cases it may be sufficient to notify the handler that a particular type of exception has occurred. However, if you do not declare an exception object in the exception declaration, you will not have access to the object in the catch handler clause. For example: catch( CTest ) { // No access to a CTest exception object in this handler. } A throw expression with no operand re-throws the exception currently being handled. Such an expression should appear only in a catch handler or in a function called from within a catch handler. The re-thrown exception object is the original exception object (not a copy). For example: try { throw CSomeOtherException(); } catch(...) // Handle all exceptions { // Respond (perhaps only partially) to exception //... throw; // Pass exception to some other handler } __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com

July 17, 2002

Re: CxxFrameHandler problem

by Alexandre Julliard

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > Appended program uses CxxFrameHandler and crashes in wine with builtin > msvcrt, but not with native. Compile as Release version and include the MFC > dll. Can somebody compile for Alexandre? Alexandre, is this a start or do > you need something complete? That's a start, yes, thanks. I'll need a more complete example with nested try blocks, destructors all over the place, typed exceptions, etc. to make sure I understand all the compiler internal structures; but I can at least try to make that simple case not crash... -- Alexandre Julliard julliard(a)winehq.com

July 17, 2002

Re: CxxFrameHandler problem

by Francois Gouget

On Wed, 17 Jul 2002, Uwe Bonnes wrote: [...] > Here at home, I only have the author's edition of VC++, not allowing my to > distributed compiled executables, but only the source. > > Appended program uses CxxFrameHandler and crashes in wine with builtin > msvcrt, but not with native. Compile as Release version and include the MFC > dll. Can somebody compile for Alexandre? Alexandre, is this a start or do > you need something complete? I compiled the program and sent it to Alexandre. I modified the program to not use iostreamsn so that I would not have to link with msvcirt.dll. I compiled with Visual C++ 6.0 in Release mode and checked that it crashes (badly) when using the builtin msvcrt. #include <stdio.h> #include <string.h> int main() { try { printf("Hello World!\n"); throw "fault"; return 1; } catch (...) { printf("Caught the exception\n"); } return 0; } trace:seh:EXC_CallHandler calling handler at 0x400c53f0 code=c0000096 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x400c53f0 code=c0000096 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x400c53f0 code=c0000096 flags=10 trace:seh:EXC_CallHandler handler returned 2 [... ad infinitum ...] -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux: the choice of a GNU generation

July 17, 2002

Re: CxxFrameHandler problem

by John K. Hohm

Alexandre Julliard <julliard(a)winehq.com> wrote: > Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > > > Appended program uses CxxFrameHandler and crashes in wine with builtin > > msvcrt, but not with native. Compile as Release version and include the > MFC > > dll. Can somebody compile for Alexandre? Alexandre, is this a start or do > > you need something complete? > > That's a start, yes, thanks. I'll need a more complete example with > nested try blocks, destructors all over the place, typed exceptions, > etc. to make sure I understand all the compiler internal structures; > but I can at least try to make that simple case not crash... Although this may duplicate effort, I am familiar with several strange combinations of exception handling that I know work with Visual C++ 6.0; I will put them a test program for you. You can never have too many test programs, right?

July 17, 2002

Re: solaris configure strangness

by Francois Gouget

On Wed, 17 Jul 2002, Shachar Shemesh wrote: [...] > checking resolv.h usability... no > checking resolv.h presence... yes > checking for resolv.h... yes > > Can anyone explain what this means? It means that: #include <resolv.h> int main() { return 0; } does not compile, but that /usr/include/resolv/h exists. In other words, resolv.h depends on other headers that you must include before including resolv.h itself.` So to have a clean configure, the above header must be moved out of the big AC_CHECK_HEADERS and into their individual checks where we can specifically test for these dependencies. See for instance XShm.h (only a vague quide). The same thing goes for the other headers. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The nice thing about meditation is that it makes doing nothing quite respectable -- Paul Dean

July 17, 2002

Re: CxxFrameHandler problem

by Uwe Bonnes

>>>>> "Alexandre" == Alexandre Julliard <julliard(a)winehq.com> writes: Alexandre> Steven Edwards <steven_ed4153(a)yahoo.com> writes: >> I dont think I can help to much with reimplementing the >> CxxFrameHandler but if anyone decides to work on it I will set aside >> plenty of time to help them debug. (Hint, Hint) =) Alexandre> The real problem is having something to seriously test it. So Alexandre> if someone (hint, hint ;-) could write a test program Alexandre> exercising the various features of C++ exceptions and send me Alexandre> a binary of it built with VC++, I'll fix CxxFrameHandler. Here at home, I only have the author's edition of VC++, not allowing my to distributed compiled executables, but only the source. Appended program uses CxxFrameHandler and crashes in wine with builtin msvcrt, but not with native. Compile as Release version and include the MFC dll. Can somebody compile for Alexandre? Alexandre, is this a start or do you need something complete? Perhaps I manage to compile tomorrow at work, but I have to leave early for a travel... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- #include <iostream.h> #include <string.h> int main() { try { cout << "Hello World!\n"; throw "fault"; return 0; } catch(...) { cerr << "Error" << endl; } }

July 17, 2002