- Wine-Devel - list.winehq.org

Re: Listview L10
by Paul Rupe Oct. 8, 2002

Oct. 8, 2002

On 07 Oct 2002, dpaun(a)rogers.com wrote: > This one fixes a lot of nasty bugs. It also fixes Xnews, > among other things. Yeah, it works great now. Cool. :) > This one should bring the listview to a decent state. > I am interested to hear about outstanding problems. One thing I noticed is that File Open/Save As dialogs in any app now show only icons (the filenames are all blank). I think this must have happened somewhere in the L-series of patches, but I haven't delved in to figure out which one yet. -- Paul Rupe "She smiled, in the end." p r u p e @ m y r e a l b o x . c o m | Oppose government police-ware on your PC! | Stop the Consumer Broadband and Digital Television Promotion Act! | <http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html>

3 2

Re: wine/dlls/rpcrt4 Makefile.in rpcrt4.spec rpcrt ...
by Greg Turner Oct. 7, 2002

Oct. 7, 2002

On Monday 07 October 2002 04:49 pm, Alexandre Julliard wrote: > ChangeSet ID: 5665 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2002/10/07 16:49:49 > > Modified files: > dlls/rpcrt4 : Makefile.in rpcrt4.spec rpcrt4_main.c > Added files: > dlls/rpcrt4 : rpc_binding.c rpc_binding.h > > Log message: > Ove Kaaven <ovek(a)transgaming.com> > Implemented RpcBindingInqObject, RpcBindingSetObject, > RpcBindingVectorFree, RpcBindingToStringBindingA/W, > RpcBindingFromStringBindingA/W, RpcStringBindingParseA/W, > I_RpcBindingSetAsync, RpcStringBindingComposeA/W, RpcBindingFree, > RPCStringFreeW, UUIDHash, UuidToStringW, and associated junk. > > Patch: http://cvs.winehq.com/patch.py?id=5665 > > Old revision New revision Changes Path > 1.8 1.9 +1 -0 wine/dlls/rpcrt4/Makefile.in > 1.19 1.20 +11 -10 wine/dlls/rpcrt4/rpcrt4.spec > 1.29 1.30 +78 -73 wine/dlls/rpcrt4/rpcrt4_main.c > Added 1.1 +0 -0 wine/dlls/rpcrt4/rpc_binding.c > Added 1.1 +0 -0 wine/dlls/rpcrt4/rpc_binding.h Interesting that you unrolled the #define macros in rpc_binding.c. I guess the argument against this is that it creates code duplication. The argument for it is more obvious (reduces insanity). In general, should I avoid submitting patches with big nasty #define's that are really inline functions like this, even at the expense of duplicating some code? Personally, I kind of dislike this sort of thing (big nasty #define's); but I notice that, to an extent, they abound in wine, and I must say that I dislike code duplication almost as much. STL is a good compromise, for C++; but obviously that doesn't help us here in C land (or does it? anyhow, STL is probably not a desirable dependency for wine IMHO). M4 is already a dependency but would be a pretty big break from the current way of doing things... if we're to drag in M4 then we'd might as well rework all of wine to use it in place of the big nasty #defines.... sounds like a miserable and tedious process, and when it's all done, nobody can understand the code (including me, and M4 ignoramus). Ugh. !%&!%& script-soup. When did coding become so much like web-page design? I blame Richard Stallman ;) Rule of thumb: Any program with backquoted backquotes is misdesigned! :) Anyhow, now that I've gotten my bitching and moaning out of the way... let me know if you'd like me to break up #defines like this in future patches and I'll do it. As for the stuff that's already checked in, I'm gonna look at the possibility of dropping some of it into RPCRT4_ functions (/real/ functions) to reduce the duplication. -- gmt "If ye love wealth better than liberty, the tranquility of servitude better than the animating contest of freedom, go home from us in peace. We ask not your counsels or your arms. Crouch down and lick the hands, which feed you. May your chains set lightly upon you, and may posterity forget that ye were our countrymen." -Samuel Adams

2 1

Re: d3d8 patch
by Christian Costa Oct. 7, 2002

Oct. 7, 2002

Ann and Jason Edmeades wrote: >Changelog: > >o Various fixes, typos corrected and clarifying trace points > >Note I am quickly reaching the end of my ability in this area - This brings >the wine tree up to date with all my changes, so some help from anyone would >be appreciated. There are some 'simple' tutorials type dx8 pgms I just cant >get working and I cant see why - email me if you can help > >Additionally, my understanding is in Windows a HAL lives under direct3d and >earlier directdraw functionality - Does anyone know where the interface is >actually documented? I have had it mentioned to me it would be better to try >to make the functionality more common with direct draw and want to see how >this is done under windows. > >Jason > Jason, The Windows HAL is documented in the DDK (Driver Development Kit). It's a package of 60MBytes or so . You can find it at : http://www.microsoft.com/ddk/ If think (but I'm not sure) the actual HAL is the Win98's one. So you should try the Win98 DDK. It's the one I use. Christian

1 0

Re: Languages/Locales
by steve.lustbader＠philips.com Oct. 7, 2002

Oct. 7, 2002

Should I resubmit this patch with the my functions moved to locale.c or ole2nls.c? Which one? Alexandre Julliard To: Steve Lustbader/ANR/MS/PHILIPS(a)AMEC <julliard(a)winehq cc: wine-devel(a)winehq.com .com> Subject: Re: Languages/Locales Sent by: wine-devel-admin Classification: @winehq.com 10/07/2002 02:02 PM steve.lustbader(a)philips.com writes: > I implemented these functions in codepage.c since similar functions > (GetDefaultLangID and GetDefaultLCID) were already there. Why are > these functions in this file, instead of in dlls/kernel/locale.c? Because they are needed by ntdll. This will be fixed eventually. > It seems locales and languages aren't really implemented yet > (just hardcoded to English) - is this going in for 1.0 or is it not planned > for the immediate future? Most of it is already implemented; the relevant stuff is in dlls/kernel/locale.c and ole/ole2nls.c. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: Listview L2
by Paul Rupe Oct. 7, 2002

Oct. 7, 2002

On 06 Oct 2002, dpaun(a)rogers.com wrote: > Another rounds of cleanups > > ChangeLog > -- Cleanup of the way we maintain/lookup the item count > -- Rename GetItemWidth to CalculateMaxWidth > -- Misc trivial changes. It looks like this one breaks Xnews again. With CVS+L0+L1+L2+my patch, the listviews all display as blank. A later patch adds a missing line "infoPtr->nItemCount = nItems;" in LISTVIEW_SetItemCount. This fixes the display problem, but I am still unable to open any newsgroups. Highlighting one and hitting Enter gives me an error from the app "List index (-1) out of bounds," suggesting that it doesn't know that anything is focused/selected. L0 and L1 appear to be fine, but L2-L8 all have this behavior. -- Paul Rupe "She smiled, in the end." p r u p e @ m y r e a l b o x . c o m | Oppose government police-ware on your PC! | Stop the Consumer Broadband and Digital Television Promotion Act! | <http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html>

2 1

is it winetest or me?
by György 'Nog' Jeney Oct. 7, 2002

Oct. 7, 2002

While cominuing on my msvcrt test, I ran accross the following anomily(mabe?). If I have ok(0 == 0, NULL) in my test, then everything works fine, but if I get ok(1 == 0, NULL) then the whole thing crashes with an exection to a write error. Anyone have any ides? nog.

2 1

is winemaker working?
by Michael Cardenas Oct. 7, 2002

Oct. 7, 2002

Hello all. I'm trying to compile a number of winelib programs that are part of the lindows-wine package. To do so, I removed all the makefiles and make.rules files and configure files, and ran winemaker --cuiexe . from the directories containing the source for runonce, geticon, and initcache. The resulting makefiles did compile, after changing the install target to strip the .exe off of the names, but the applications do not run. They look for <appname>.exe in C:\windows\system, but even if I put the apps in that dir with that name, they still don't run and complain tht they can't find <appname>.exe So, is anyone using winemaker? Has anyone used it to make a simple winelib app recently? Does it still work? There seem to have been a lot of changes to the spec file format recently, which have probably rendered it unusable. thanks michael -- michael cardenas | lead software engineer lindows.com hyperpoem.net | GNU/Linux software developer debian.org "What the poet is looking for is not the fundamental I but the deep you." - Antonio Machado

3 2

Re: DOS DPMI32, interrupt handlers in 32-bit code
by Sylvain Petreolle Oct. 7, 2002

Oct. 7, 2002

Hi Jukka, I tried your patch on the latest CVS. This doesn't compile at the moment, complaining about FARPROC48 : gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ -D_NTSYSTEM_ -DBINDIR="\"/usr/local/bin\"" -DETCDIR="\"/usr/local/etc\"" -D_REENTRANT -o ../../memory/instr.o ../../memory/instr.c../../memory/instr.c: In function `INSTR_EmulateInstruction': ../../memory/instr.c:689: `FARPROC48' undeclared (first use in this function) ../../memory/instr.c:689: (Each undeclared identifier is reported only once ../../memory/instr.c:689: for each function it appears in.) ../../memory/instr.c:689: parse error before "addr" ../../memory/instr.c:697: `addr' undeclared (first use in this function) make[2]: *** [../../memory/instr.o] Erreur 1 ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 2

Re: How to add a new test dir? (Update)
by Greg Turner Oct. 7, 2002

Oct. 7, 2002

On Sunday 06 October 2002 06:25 pm, Greg Turner wrote: > I'm trying to create a tests directory for rpcrt4. So far I've > done the following: > > o Create a dlls/rpcrt4/tests directory > > o Change dlls/rpcrt4/Makefile.in: > > o add dlls/rpcrt4/tests/Makefile.in: > > o add dlls/rpcrt4/tests/rpc.c: > > but I get no love. configure seems to go OK; > When I run make depend it fails: > > <============== > make[2]: Entering directory `/var/src/wine/dlls/rpcrt4' > cd `dirname tests/__depend__` && make depend > make[3]: Entering directory `/var/src/wine/dlls/rpcrt4/tests' > make[3]: *** No rule to make target `depend'. Stop. > make[3]: Leaving directory `/var/src/wine/dlls/rpcrt4/tests' > make[2]: *** [tests/__depend__] Error 2 > make[2]: Leaving directory `/var/src/wine/dlls/rpcrt4' > make[1]: *** [rpcrt4/__depend__] Error 2 > make[1]: Leaving directory `/var/src/wine/dlls' > make: *** [dlls/__depend__] Error 2 > ==============> > > What am I missing? Is this documented somewhere? > Thanks, I found it: Index: configure.ac =================================================================== RCS file: /home/wine/wine/configure.ac,v retrieving revision 1.81 diff -u -r1.81 configure.ac --- configure.ac 2 Oct 2002 19:58:27 -0000 1.81 +++ configure.ac 7 Oct 2002 03:09:02 -0000 @@ -1435,6 +1435,7 @@ dlls/rasapi32/Makefile dlls/richedit/Makefile dlls/rpcrt4/Makefile +dlls/rpcrt4/tests/Makefile dlls/serialui/Makefile dlls/setupapi/Makefile dlls/shdocvw/Makefile Now I'm sure it'll get even more confusing ;) -- gmt "If ye love wealth better than liberty, the tranquility of servitude better than the animating contest of freedom, go home from us in peace. We ask not your counsels or your arms. Crouch down and lick the hands, which feed you. May your chains set lightly upon you, and may posterity forget that ye were our countrymen." -Samuel Adams

1 0

pain and agony... a +relay,+seh trace from my cxxexcept problem case:
by Greg Turner Oct. 6, 2002

Oct. 6, 2002

OK, here is what looks to me like the relevant stuff... I'm determined to get this fixed, I "need" this app (ya right... I've got vmware...) =================> 0807bf40:Ret ws2_32.recv() retval=00000010 ret=410d966a 0807bf40:Call ws2_32.recv(00000174,42a908b0,0000004d,00000000) ret=410d966a 0807bf40:Call ntdll.wine_server_handle_to_fd(00000174,80000000,406f1cec,406f1d54,406f1d64) ret=411976f5 0807bf40:Ret ntdll.wine_server_handle_to_fd() retval=00000000 ret=411976f5 0807bf40:Call kernel32.GetProcessHeap() ret=4119693e 0807bf40:Ret kernel32.GetProcessHeap() retval=403d0000 ret=4119693e 0807bf40:Call ntdll.RtlAllocateHeap(403d0000,00000000,00000008) ret=4119695a 0807bf40:Ret ntdll.RtlAllocateHeap() retval=404d1be8 ret=4119695a 0807bf40:Call kernel32.GetProcessHeap() ret=41196c0c 0807bf40:Ret kernel32.GetProcessHeap() retval=403d0000 ret=41196c0c 0807bf40:Call ntdll.RtlFreeHeap(403d0000,00000000,404d1be8) ret=41196c25 0807bf40:Ret ntdll.RtlFreeHeap() retval=00000001 ret=41196c25 0807bf40:Ret ws2_32.recv() retval=0000004d ret=410d966a 0807bf40:Call msvcrt.malloc(00000008) ret=5f40384f 0807bf40:Call kernel32.GetProcessHeap() ret=40f216bf 0807bf40:Ret kernel32.GetProcessHeap() retval=403d0000 ret=40f216bf 0807bf40:Call ntdll.RtlAllocateHeap(403d0000,00000000,00000008) ret=40f216d6 0807bf40:Ret ntdll.RtlAllocateHeap() retval=404d1be8 ret=40f216d6 0807bf40:Ret msvcrt.malloc() retval=404d1be8 ret=5f40384f <================ so far, so good, right? Looks like pretty normal stuff going on here; the exception is raised by proprietary code within starteam, but they like to catch their own exceptions, I think it's supposed to pass and be handled. In the debugger, the stack looks great, goes back cleanly all the way to init. =================> 0807bf40:Call msvcrt._CxxThrowException(406f1f4c,410dff80) ret=410d4d0a 0807bf40:Call kernel32.RaiseException(e06d7363,00000001,00000003,406f1e24) ret=40f15b9e trace:seh:EXC_RtlRaiseException code=e06d7363 flags=1 addr=0x401060f4 trace:seh:EXC_RtlRaiseException info[0]=19930520 trace:seh:EXC_RtlRaiseException info[1]=406f1f4c trace:seh:EXC_RtlRaiseException info[2]=410dff80 trace:seh:EXC_CallHandler calling handler at 0x410de5e6 code=e06d7363 flags=1 0807bf40:Call msvcrt.__CxxFrameHandler(406f1cc4,406f1f68,406f1960,406f1940) ret=4010c420 fs=008f eax=410dff20 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1f70 edi=406f195c ebp=406f18a4 esp=406f1860 ds=002b es=002b gs=0000 flags=00000212 0807bf40:Ret msvcrt.__CxxFrameHandler() retval=00000001 ret=4010c420 fs=008f eax=00000001 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1f70 edi=406f195c ebp=406f18a4 esp=406f1860 ds=002b es=002b gs=0000 flags=00000212 trace:seh:EXC_CallHandler handler returned 1 <=============== OK, one handler called, ExceptionContinueSearch. now here comes something more significant.... =============> trace:seh:EXC_CallHandler calling handler at 0x410de4b4 code=e06d7363 flags=1 0807bf40:Call msvcrt.__CxxFrameHandler(406f1cc4,406f1fc8,406f1960,406f1940) ret=4010c420 fs=008f eax=410dfc20 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1fd0 edi=406f195c ebp=406f18a4 esp=406f1860 ds=002b es=002b gs=0000 flags=00000212 trace:seh:cxx_frame_handler handling C++ exception rec 0x406f1cc4 frame 0x406f1fc8 trylevel 0 descr 0x410dfc20 exception type: flags 0 destr (nil) handler (nil) type info 0x410dff68 0: flags 1 type 0x410e4400 ((nil) .PAVCStCommandExceptionDetected@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 1: flags 1 type 0x410e43e0 ((nil) .PAVCException@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 2: flags 1 type 0x410e4440 ((nil) .PAVCObject@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 3: flags 1 type 0x410e4430 ((nil) .PAX) offset 0 vbase -1,0 size 4 copy ctor (nil) function descr: magic 19930520 unwind table: 0x410dfc40 4 0: prev -1 func (nil) 1: prev -1 func (nil) 2: prev 1 func (nil) 3: prev 1 func (nil) try table: 0x410dfc60 2 0: start 2 end 2 catchlevel 3 catch 0x410dfc88 1 0: flags 0 offset -28 handler 0x410d2b63 type 0x410e43e0 ((nil) .PAVCException@@) 1: start 0 end 0 catchlevel 3 catch 0x410dfc98 2 0: flags 0 offset -24 handler 0x410d2b36 type 0x410e4400 ((nil) .PAVCStCommandExceptionDetected@@) 1: flags 0 offset 0 handler 0x410d2b52 type (nil) trace:seh:call_catch_block matched type 0x410dff48 in tryblock 1 catchblock 0 <============ allright, obviously we're in cxx_frame_handler, at "normal_handler:". So far, everyone seems happy. Off we go into call_catch_block ============> trace:seh:EXC_RtlUnwind code=e06d7363 flags=3 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=e06d7363 flags=3 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x410de5e6 code=e06d7363 flags=3 0807bf40:Call msvcrt.__CxxFrameHandler(406f1cc4,406f1f68,406f0ea4,406f0dd8) ret=4010c420 fs=008f eax=410dff20 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1f70 edi=406f0ea0 ebp=406f0da0 esp=406f0d5c ds=002b es=002b gs=0000 flags=00000216 0807bf40:Ret msvcrt.__CxxFrameHandler() retval=00000001 ret=4010c420 fs=008f eax=00000001 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1f70 edi=406f0ea0 ebp=406f0da0 esp=406f0d5c ds=002b es=002b gs=0000 flags=00000216 trace:seh:EXC_CallHandler handler returned 1 0807bf40:Ret ntdll.RtlUnwind() retval=00000000 ret=40f15d99 <========== Presumably we're still in call_catch_block, really justin the RtlUnwind parts. Now the catch block is called... ============> trace:seh:call_catch_block calling catch block 0x410dfc98 for type 0x410dff48 addr 0x410d2b36 ebp 0x406f1fd4 0807bf40:Call msvcrt.free(404d1be8) ret=5f40388b 0807bf40:Call kernel32.GetProcessHeap() ret=40f21687 0807bf40:Ret kernel32.GetProcessHeap() retval=403d0000 ret=40f21687 0807bf40:Call ntdll.RtlFreeHeap(403d0000,00000000,404d1be8) ret=40f216a0 0807bf40:Ret ntdll.RtlFreeHeap() retval=00000001 ret=40f216a0 0807bf40:Ret msvcrt.free() retval=00000001 ret=5f40388b 0807bf40:Call msvcrt.malloc(00000050) ret=5f40384f 0807bf40:Call kernel32.GetProcessHeap() ret=40f216bf 0807bf40:Ret kernel32.GetProcessHeap() retval=403d0000 ret=40f216bf 0807bf40:Call ntdll.RtlAllocateHeap(403d0000,00000000,00000050) ret=40f216d6 0807bf40:Ret ntdll.RtlAllocateHeap() retval=404d55d8 ret=40f216d6 0807bf40:Ret msvcrt.malloc() retval=404d55d8 ret=5f40384f 0807bf40:Call msvcrt.memcpy(406f1234,42a908b0,00000004) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f1234 ret=410d4a2e 0807bf40:Call msvcrt.memcpy(406f11fc,42a908b4,00000012) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f11fc ret=410d4a2e 0807bf40:Call ntdll.RtlEnterCriticalSection(5f4d0088) ret=5f4020bd 0807bf40:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=5f4020bd 0807bf40:Call ntdll.RtlLeaveCriticalSection(5f4d0088) ret=5f402103 0807bf40:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=5f402103 0807bf40:Call msvcrt.memcpy(42a902c0,5f4d1b58,00000001) ret=5f402676 0807bf40:Ret msvcrt.memcpy() retval=42a902c0 ret=5f402676 0807bf40:Call msvcrt.memcpy(406f1234,42a908c6,00000004) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f1234 ret=410d4a2e 0807bf40:Call msvcrt.memcpy(406f1294,42a908ca,00000004) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f1294 ret=410d4a2e 0807bf40:Call msvcrt.memcpy(406f1290,42a908ce,00000004) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f1290 ret=410d4a2e 0807bf40:Call msvcrt.memcpy(404d5600,42a908d2,00000004) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=404d5600 ret=410d4a2e 0807bf40:Call msvcrt.memcpy(404d55f8,42a908d6,00000008) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=404d55f8 ret=410d4a2e 0807bf40:Call msvcrt.memcpy(406f1234,42a908de,00000004) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f1234 ret=410d4a2e 0807bf40:Call msvcrt.memcpy(406f11f8,42a908e2,00000017) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f11f8 ret=410d4a2e 0807bf40:Call ntdll.RtlEnterCriticalSection(5f4d0088) ret=5f4020bd 0807bf40:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=5f4020bd 0807bf40:Call ntdll.RtlLeaveCriticalSection(5f4d0088) ret=5f402103 0807bf40:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=5f402103 0807bf40:Call msvcrt.memcpy(42a90310,5f4d1b58,00000001) ret=5f402676 0807bf40:Ret msvcrt.memcpy() retval=42a90310 ret=5f402676 0807bf40:Call msvcrt.memcpy(406f122c,42a908f9,00000004) ret=410d4a2e 0807bf40:Ret msvcrt.memcpy() retval=406f122c ret=410d4a2e 0807bf40:Call msvcrt.malloc(00000194) ret=5f40384f 0807bf40:Call kernel32.GetProcessHeap() ret=40f216bf 0807bf40:Ret kernel32.GetProcessHeap() retval=403d0000 ret=40f216bf 0807bf40:Call ntdll.RtlAllocateHeap(403d0000,00000000,00000194) ret=40f216d6 0807bf40:Ret ntdll.RtlAllocateHeap() retval=42aeaf30 ret=40f216d6 0807bf40:Ret msvcrt.malloc() retval=42aeaf30 ret=5f40384f 0807bf40:Call msvcrt.memset(42aeaf30,00000000,00000194) ret=410d3b8b 0807bf40:Ret msvcrt.memset() retval=42aeaf30 ret=410d3b8b 0807bf40:Call msvcrt._CxxThrowException(406f12b0,410dfdf8) ret=410d2f3c <=============== The handler wants to raise a new exception. ===============> 0807bf40:Call kernel32.RaiseException(e06d7363,00000001,00000003,406f1190) ret=40f15b9e trace:seh:EXC_RtlRaiseException code=e06d7363 flags=1 addr=0x401060f4 trace:seh:EXC_RtlRaiseException info[0]=19930520 trace:seh:EXC_RtlRaiseException info[1]=406f12b0 trace:seh:EXC_RtlRaiseException info[2]=410dfdf8 trace:seh:EXC_CallHandler calling handler at 0x410de4e6 code=e06d7363 flags=1 0807bf40:Call msvcrt.__CxxFrameHandler(406f1030,406f12c8,406f0ccc,406f0cac) ret=4010c420 fs=008f eax=410dfce8 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f12d0 edi=406f0cc8 ebp=406f0c10 esp=406f0bcc ds=002b es=002b gs=0000 flags=00000216 0807bf40:Ret msvcrt.__CxxFrameHandler() retval=00000001 ret=4010c420 fs=008f eax=00000001 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f12d0 edi=406f0cc8 ebp=406f0c10 esp=406f0bcc ds=002b es=002b gs=0000 flags=00000216 trace:seh:EXC_CallHandler handler returned 1 <=============== looks familiar, we're at normal_handler again, and calling call_catch_block once more...? ================> trace:seh:EXC_CallHandler calling handler at 0x410de4b4 code=e06d7363 flags=1 0807bf40:Call msvcrt.__CxxFrameHandler(406f1030,406f1fc8,406f0ccc,406f0cac) ret=4010c420 fs=008f eax=410dfc20 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1fd0 edi=406f0cc8 ebp=406f0c10 esp=406f0bcc ds=002b es=002b gs=0000 flags=00000216 trace:seh:cxx_frame_handler handling C++ exception rec 0x406f1030 frame 0x406f1fc8 trylevel 1 descr 0x410dfc20 exception type: flags 0 destr (nil) handler (nil) type info 0x410dfde0 0: flags 1 type 0x410e4478 ((nil) .PAVCStBaseServerException@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 1: flags 1 type 0x410e4458 ((nil) .PAVCStException@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 2: flags 1 type 0x410e43e0 ((nil) .PAVCException@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 3: flags 1 type 0x410e4440 ((nil) .PAVCObject@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 4: flags 1 type 0x410e4430 ((nil) .PAX) offset 0 vbase -1,0 size 4 copy ctor (nil) function descr: magic 19930520 unwind table: 0x410dfc40 4 0: prev -1 func (nil) 1: prev -1 func (nil) 2: prev 1 func (nil) 3: prev 1 func (nil) try table: 0x410dfc60 2 0: start 2 end 2 catchlevel 3 catch 0x410dfc88 1 0: flags 0 offset -28 handler 0x410d2b63 type 0x410e43e0 ((nil) .PAVCException@@) 1: start 0 end 0 catchlevel 3 catch 0x410dfc98 2 0: flags 0 offset -24 handler 0x410d2b36 type 0x410e4400 ((nil) .PAVCStCommandExceptionDetected@@) 1: flags 0 offset 0 handler 0x410d2b52 type (nil) 0807bf40:Ret msvcrt.__CxxFrameHandler() retval=00000001 ret=4010c420 fs=008f eax=00000001 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1fd0 edi=406f0cc8 ebp=406f0c10 esp=406f0bcc ds=002b es=002b gs=0000 flags=00000216 trace:seh:EXC_CallHandler handler returned 1 <============ looks like it wasn't interested... Not sure if I really understand what happened there... ===========> trace:seh:EXC_CallHandler calling handler at 0x410a5add code=e06d7363 flags=1 0807bf40:Call msvcrt.__CxxFrameHandler(406f1030,406f2108,406f0ccc,406f0cac) ret=4010c420 fs=008f eax=410ab3f8 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f2110 edi=406f0cc8 ebp=406f0c10 esp=406f0bcc ds=002b es=002b gs=0000 flags=00000216 trace:seh:cxx_frame_handler handling C++ exception rec 0x406f1030 frame 0x406f2108 trylevel 1 descr 0x410ab3f8 exception type: flags 0 destr (nil) handler (nil) type info 0x410dfde0 0: flags 1 type 0x410e4478 ((nil) .PAVCStBaseServerException@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 1: flags 1 type 0x410e4458 ((nil) .PAVCStException@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 2: flags 1 type 0x410e43e0 ((nil) .PAVCException@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 3: flags 1 type 0x410e4440 ((nil) .PAVCObject@@) offset 0 vbase -1,0 size 4 copy ctor (nil) 4: flags 1 type 0x410e4430 ((nil) .PAX) offset 0 vbase -1,0 size 4 copy ctor (nil) function descr: magic 19930520 unwind table: 0x410ab418 7 0: prev -1 func (nil) 1: prev 0 func (nil) 2: prev 1 func 0x410a5abd 3: prev 2 func 0x410a5ac6 4: prev 3 func 0x410a5acf 5: prev 0 func (nil) 6: prev -1 func (nil) try table: 0x410ab450 2 0: start 1 end 4 catchlevel 5 catch 0x410ab478 2 0: flags 0 offset -80 handler 0x41082e43 type 0x410b5070 ((nil) .PAVCException@@) 1: flags 0 offset 0 handler 0x41082e6d type (nil) 1: start 0 end 5 catchlevel 6 catch 0x410ab498 2 0: flags 0 offset -84 handler 0x41082e9c type 0x410b5070 ((nil) .PAVCException@@) 1: flags 0 offset 0 handler 0x41082eb9 type (nil) trace:seh:call_catch_block matched type 0x410dfd80 in tryblock 0 catchblock 0 <============= Allright, I'm kind of lost now, but we've obviously found our way back into normal_handler once more, and this time call_catch_block is going to take some action, calling back into Starteam once more; first it does the RtlUnwind ritual: ============> 0807bf40:Call ntdll.RtlUnwind(406f2108,00000000,406f1030,00000000) ret=40f15d99 trace:seh:EXC_RtlUnwind code=e06d7363 flags=3 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=e06d7363 flags=3 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x410de4e6 code=e06d7363 flags=3 0807bf40:Call msvcrt.__CxxFrameHandler(406f1030,406f12c8,406f0210,406f0144) ret=4010c420 fs=008f eax=410dfce8 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f12d0 edi=406f020c ebp=406f010c esp=406f00c8 ds=002b es=002b gs=0000 flags=00000202 0807bf40:Ret msvcrt.__CxxFrameHandler() retval=00000001 ret=4010c420 fs=008f eax=00000001 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f12d0 edi=406f020c ebp=406f010c esp=406f00c8 ds=002b es=002b gs=0000 flags=00000202 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x410de4b4 code=e06d7363 flags=3 0807bf40:Call msvcrt.__CxxFrameHandler(406f1030,406f1fc8,406f0210,406f0144) ret=4010c420 fs=008f eax=410dfc20 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1fd0 edi=406f020c ebp=406f010c esp=406f00c8 ds=002b es=002b gs=0000 flags=00000202 0807bf40:Ret msvcrt.__CxxFrameHandler() retval=00000001 ret=4010c420 fs=008f eax=00000001 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f1fd0 edi=406f020c ebp=406f010c esp=406f00c8 ds=002b es=002b gs=0000 flags=00000202 trace:seh:EXC_CallHandler handler returned 1 0807bf40:Ret ntdll.RtlUnwind() retval=00000000 ret=40f15d99 <============= Allright, here it goes. ==============> trace:seh:call_catch_block calling catch block 0x410ab478 for type 0x410dfd80 addr 0x41082e43 ebp 0x406f2114 0807bf40:Call ntdll.RtlLeaveCriticalSection(42a00434) ret=41085594 0807bf40:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=41085594 0807bf40:Call msvcrt.clock() ret=40f3e262 0807bf40:Ret msvcrt.clock() retval=0000d354 ret=40f3e262 0807bf40:Call ntdll._ftol() ret=40f3e279 0807bf40:Ret ntdll._ftol() retval=0000d354 ret=40f3e279 0807bf40:Call kernel32.lstrcpynA(406ee63c,42a90310 "Event Handler not found",00002000) ret=4104386c 0807bf40:Ret kernel32.lstrcpynA() retval=406ee63c ret=4104386c 0807bf40:Call kernel32.lstrlenA(406ee63c "Event Handler not found") ret=5f4038e2 0807bf40:Ret kernel32.lstrlenA() retval=00000017 ret=5f4038e2 0807bf40:Call ntdll.RtlEnterCriticalSection(5f4d0088) ret=5f4020bd 0807bf40:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=5f4020bd 0807bf40:Call ntdll.RtlLeaveCriticalSection(5f4d0088) ret=5f402103 0807bf40:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=5f402103 0807bf40:Call msvcrt.memcpy(42a90360,406ee63c,00000017) ret=5f403910 0807bf40:Ret msvcrt.memcpy() retval=42a90360 ret=5f403910 0807bf40:Call msvcrt._CxxThrowException(00000000,00000000) ret=41082e6d <============== StarTeam wants to re-raise again. So now, if I understand correctly, they're going to nest another Raise within the already nested Raise. That's it for Starteam. >From here on out, it's all wine. This is where TSHTF. Note that this time, the arguments to ThrowException are both NULL... ostensibly (to me ;) this is the root of the problem. ==============> 0807bf40:Call kernel32.RaiseException(e06d7363,00000001,00000003,406f0530) ret=40f15b9e trace:seh:EXC_RtlRaiseException code=e06d7363 flags=1 addr=0x401060f4 trace:seh:EXC_RtlRaiseException info[0]=19930520 trace:seh:EXC_RtlRaiseException info[1]=00000000 trace:seh:EXC_RtlRaiseException info[2]=00000000 <============= info[1] and [2] come from the ThrowException arguments (NULL, and NULL of course). At this point, in cxx_excpeption_handler, info[2] becomes exc_type, and gets deferenced: exc_type = (cxx_exception_type *)rec->ExceptionInformation[2]; if (rec->ExceptionCode != CXX_EXCEPTION) goto normal_handler; if (rec->ExceptionInformation[0] != CXX_FRAME_MAGIC) goto normal_handler; if (exc_type->custom_handler) <<<<<<<<<< SEGFAULT on NULL pointer deference here Now chaos ensues: ===============> trace:seh:EXC_CallHandler calling handler at 0x410a5add code=e06d7363 flags=1 0807bf40:Call msvcrt.__CxxFrameHandler(406f03d0,406f2108,406f006c,406f004c) ret=4010c420 fs=008f eax=410ab3f8 ebx=40149d30 ecx=401614a8 edx=00000034 esi=406f2110 edi=406f0068 ebp=406effb0 esp=406eff6c ds=002b es=002b gs=0000 flags=00000216 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x40f159a3 trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=00000008 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x410a5add code=c0000005 flags=10 0807bf40:Call msvcrt.__CxxFrameHandler(405e09d8,406f2108,405e0a44,405e099c) ret=4010c420 fs=008f eax=410ab3f8 ebx=40149d30 ecx=401614a8 edx=00000035 esi=406f2110 edi=00000004 ebp=405e0900 esp=405e08bc ds=002b es=002b gs=0000 flags=00000212 trace:seh:cxx_frame_handler handling C++ exception rec 0x405e09d8 frame 0x406f2108 trylevel 5 descr 0x410ab3f8 exception type: trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x40f151f5 trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=0000000c trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x410a5add code=c0000005 flags=10 0807bf40:Call msvcrt.__CxxFrameHandler(405dfd68,406f2108,405dfdd4,405dfd2c) ret=4010c420 fs=008f eax=410ab3f8 ebx=40149d30 ecx=401614a8 edx=00000035 esi=406f2110 edi=00000004 ebp=405dfc90 esp=405dfc4c ds=002b es=002b gs=0000 flags=00000212 trace:seh:cxx_frame_handler handling C++ exception rec 0x405dfd68 frame 0x406f2108 trylevel 5 descr 0x410ab3f8 exception type: trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x40f151f5 trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=0000021e trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x410a5add code=c0000005 flags=10 0807bf40:Call msvcrt.__CxxFrameHandler(405df0f8,406f2108,405df164,405df0bc) ret=4010c420 fs=008f eax=410ab3f8 ebx=40149d30 ecx=401614a8 edx=00000035 esi=406f2110 edi=00000004 ebp=405df020 esp=405defdc ds=002b es=002b gs=0000 flags=00000212 trace:seh:cxx_frame_handler handling C++ exception rec 0x405df0f8 frame 0x406f2108 trylevel 5 descr 0x410ab3f8 exception type: trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x40f151f5 trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=0000021e trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4010c310 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x410a5add code=c0000005 flags=10 <============ and so on. What have we learned, except that StarTeam was probably written in Visual Basic? Not sure. I guess I need to focus on: "where are the NULL's passed to ThrowException coming from?"?? Or is there something more obvious going on here that I'm to ign'ant to grok? thanks for your help,... -- gmt "If ye love wealth better than liberty, the tranquility of servitude better than the animating contest of freedom, go home from us in peace. We ask not your counsels or your arms. Crouch down and lick the hands, which feed you. May your chains set lightly upon you, and may posterity forget that ye were our countrymen." -Samuel Adams

2 2