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

Re: Any advice on how to debug this?

by Alexandre Julliard

"Medland, Bill" <Bill.Medland(a)accpac.com> writes: > It looks to me like: > > comctl32.dll includes a shared data segment. > One of the entries in that segment, presumably during the DllEntry, is > populated with the address of GetSystemMetrics > > A second copy of comctl32 then tries to use that address to call > GetSystemMetrics > > Unfortunately the second process has user32 mapped somewhere else and so the > call goes somewhere weird and things fall over. > > Any ideas as to what we can do about it? That's a common problem with Win9x dlls. It cannot be completely fixed because we don't control the layout of our address space; there are some hacks that could be done in the loader to make it less likely to happen, but I'm not convinced it is worth the trouble. Our efforts would probably be better spent making sure the builtin versions of the offending dlls work properly. -- Alexandre Julliard julliard(a)winehq.com

July 10, 2002

Re: winedbg font selection?

by Michael Cardenas

Andreas Mohr wrote: >On Wed, Jul 10, 2002 at 10:50:03AM -0400, Carl Sopchak wrote: > > >>Is there a way to set the font used by winedbg? The font that it is using on >>my machine is too small with the monitor resolution set at 1600x1200 (which I >>want to keep). I'd like to bump the size up a few points... >> >> >Of course you're aware of the fact that wineconsole has a context menu, >right ? > >;-)) > >Andreas "Why does nobody ever realize simple things" Mohr > > Well, that's the problem with context menus, by definition, they're hidden. Although, since xterm has one, I guess I should've figured that one out too. But do you really want to change the size every time it launches? not if you're actually doing some debugging. and I've read the debugger documentation on winehq, and I don't recall that menu being mentioned. -- michael cardenas lead windows compatibility engineer lindows.com . hyperpoem.net . "Be the change you want to see in the world" -Mahatma Gandhi

July 10, 2002

Re: winedbg font selection?

by Eric Pouech

Carl Sopchak a écrit : > > Is there a way to set the font used by winedbg? The font that it is using on > my machine is too small with the monitor resolution set at 1600x1200 (which I > want to keep). I'd like to bump the size up a few points... for the Nth time: in the wineconsole, right click and choose default in the menu in the dialog, select the 'font' thumb and choose the font you want (facename & size) then close the dlg box with ok A+

July 10, 2002

Re: winedbg font selection?

by Andreas Mohr

On Wed, Jul 10, 2002 at 10:50:03AM -0400, Carl Sopchak wrote: > Is there a way to set the font used by winedbg? The font that it is using on > my machine is too small with the monitor resolution set at 1600x1200 (which I > want to keep). I'd like to bump the size up a few points... Of course you're aware of the fact that wineconsole has a context menu, right ? ;-)) Andreas "Why does nobody ever realize simple things" Mohr

July 10, 2002

Re: Meta-bug conversions

by Michael Cardenas

Francois Gouget wrote: >... >I propose to use what would hopefully be better concepts to replace the >following meta-bugs: > > * bug 35 - Wine 0.9.0 Meta Bug > http://bugs.winehq.com/showdependencytree.cgi?id=35 > > Instead we could tag all the bug that should be fixed in Wine 0.9.0 >with the 0.9.0 target milestone. > > * bug 395 - Tasklist > http://bugs.winehq.com/showdependencytree.cgi?id=395 > * bug 455 - FIXMEs > http://bugs.winehq.com/showdependencytree.cgi?id=455 > * bug 406- Tasklets > http://bugs.winehq.com/showdependencytree.cgi?id=406 > > These three could be replaced by keywords: Tasklist, FIXMEs and >Tasklets. Then these bugs can be replaced with a query that returns the >bugs that have these keywords. > >... > I agree that this would be much better. At lindows, we use a system just like the one you described here in our bugzilla because it's so important to be able to easily query the pending bugs for a release, which changes rapidly and often. -- michael cardenas lead windows compatibility engineer lindows.com . hyperpoem.net . "Be the change you want to see in the world" -Mahatma Gandhi

July 10, 2002

Re: winedbg font selection?

by Michael Cardenas

Carl Sopchak wrote: >Is there a way to set the font used by winedbg? The font that it is using on >my machine is too small with the monitor resolution set at 1600x1200 (which I >want to keep). I'd like to bump the size up a few points... > >Thanks for the help, > >Carl > > I'd love to know how to do this also. I have settings in my ~/.Xdefaults file for xterm, which winedbg seems to use when it gets launched, but they don't work. My guess is that you'd have to add a line to your ~/.Xdefaults file for winedbg. Here are my entries for emacs and xterm, but I'm not sure how to do it for winedbg, a coworker of mine wrote this Xdefaults and I just got a copy of his. --- #define FIXED14 -*-lucidatypewriter-*-r-normal-sans-14-140-75-75-m-90-iso8859-1 #if HEIGHT == 1024 emacs*font:FIXED14 emacs*geometry: 80x64+524-0 !emacs*geometry: 80x60-0-0 xterm.vt100.Font:FIXED14 xterm.vt100.geometry: 80x58+0-0 #endif -- michael cardenas lead windows compatibility engineer lindows.com . hyperpoem.net . "Be the change you want to see in the world" -Mahatma Gandhi

July 10, 2002

RE: Any advice on how to debug this?

by Medland, Bill

> -----Original Message----- > From: Eric Pouech [mailto:eric.pouech(a)wanadoo.fr] > Sent: Wednesday, July 10, 2002 4:59 AM > To: Medland, Bill > Cc: Wine devel (E-mail) > Subject: Re: Any advice on how to debug this? > > > > The stack traces in both cases are similar and indicate to > me that the > > processes have ended up executing data. > > However by the time I get to disassemble the code referred to by the > > backtrace the code isn't there any longer. > is most of the cases, it means that the program is no longer > running (it > may > have been killed by the other program) > > > What's my best bet for tracking this down? > as the processes seem to be furtive, using relay traces (and friends) > may be > a better bet to locate the issue, and then perhaps set the bp where > needed > > A+ > Thanks Eric. So now what do we do. Having messed about, got a repeatable case and generally bashed my head around I have got to the following unfortunate situation. It looks to me like: comctl32.dll includes a shared data segment. One of the entries in that segment, presumably during the DllEntry, is populated with the address of GetSystemMetrics A second copy of comctl32 then tries to use that address to call GetSystemMetrics Unfortunately the second process has user32 mapped somewhere else and so the call goes somewhere weird and things fall over. Any ideas as to what we can do about it? Bill

July 10, 2002

Re: RFC: Re: [ros-kernel] Shell32 and dplax

by Steven Edwards

--- Eric Pouech <eric.pouech(a)wanadoo.fr> wrote: > Steven Edwards a �crit : > > > > > in short, moving to NT architecture is the way > to > > > go, but > > > it'll need some time > > > may be we could also create a metabug on > bugzilla > > > for this > > > and link all known issues to this meta-bug. > > > > I will start a meta bug for this and being to > track > > these issues as I find them. With any luck we will > be > > able to help with these issues in the next few > months. > ok > btw, is this intentional ? (you didn't cc > wine-devel) no it wasnt. but yes I will start a meta-bug for these issues and wait on input from the bugzilla guys as to if they want to group the issues in another way. Steven __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com

July 10, 2002

Re: RFC: Re: [ros-kernel] Shell32 and dplax

by KJK::Hyperion

At 08.15 09/07/2002, you wrote: >MapSL >ConvertToGlobalHandle what are these two for? I've never heard them >PSAPI I'm (was) working on PSAPI, but it's obviously based on the NT API. The module enumeration (not done yet - I have to dig down the LDR structures) will require a memory layout that matches NT's down to the byte - specifically, all processes must have a PEB, and it must be exactly identical to NT's. I think the Wine guys should better keep their toolhelp-based implementation. It's an especially "delicate" area

July 10, 2002

Re: about XIM support on wine

by Mike McCormack

Hi, The best solution for the time being is to use Over-the-top entry, so that characters you type are shown in a small child window rather than a seperate window. If you're feeling keen, then you could try and interface XIM to Microsoft's own input context stuff (see ImmGetContext in imm32.dll). Do you have any patches for us to try out? Mike rain shaw wrote: > Hi all, > I do apply some patches to the wine source according to some tips in > bugs library,and I can input chinese in notepad now. > But,every time window was created,will the input method popup.For > example,if a message box popped up,the xim will popup as well. > It seems that we called the XIM related Xlib function every time new > window was created. > Would u please give me some suggestions about how to disable create and > open XIM while create non-text-input related window? in other word,how > to determin the x-window that going to be created is a control that need > input method ? > Thanx!

July 10, 2002