Re: winedbg hanging

2005-02-26 Thread Alex Woods
On Sat, Feb 26, 2005 at 09:00:04PM +, Alex Woods wrote: > as 64-bit? I'm pretty sure I'm either being dense, or something is > happening that I'm not aware of. Could someone point out which, please? It was a bit of both. There is a dbghelp.dll in the apps directory. I'm off to wallow in sha

Re: vartest.c - major pain in the build process

2005-02-26 Thread Krzysztof Foltman
Jakob Eriksson wrote: Also, that won't stop people from running winetest on linux, I'll bet $5 winetest.exe downloads from WRT will keep showing up. Yes. But should something that's useless for the majority of users and developers be enabled by default ? Looks like significant cost with little be

winedbg hanging

2005-02-26 Thread Alex Woods
Hello, When I try to run winedbg with the --gdb option, it simply hangs. I've tracked this down to dbg_get_debuggee_info returning false and then everything falling through to a wait(NULL). The callback that is getting passed SymEnumerateModules doesn't seem to be getting called at all. I've pu

Re: MSVCRT: Generating relay stubs for libc forwards/varargs

2005-02-26 Thread Jon Griffiths
> For the varargs and libc-forwarded function in msvcrt, I think all > that we > need is already in out spec file. So no need for the MS SDK. If you want to write the tracing code by hand, yes. If you have the headers winedump will generate the TRACE() statements for you as well. Cheers, Jon ==

Re: vartest.c - major pain in the build process

2005-02-26 Thread Jakob Eriksson
Mike Hearn wrote: I disable winetest in my tree entirely, and have done for a long time. It should be disabled in CVS as well, nobody should be building winetest on Linux, it just encourages people to submit useless results by saying "oooh I wonder what happens if I do this". Worse this isn't just

Re: MSVCRT: Generating relay stubs for libc forwards/varargs

2005-02-26 Thread Alexandre Julliard
Uwe Bonnes <[EMAIL PROTECTED]> writes: > in msvcrt a lot of functions are of type vararg (e.g. printf) or are > forwards into the Linux libc (e.g. strstr) and so leave no trace in a +relay > log. This makes it harder to debug. The forwards into libc show up in relay just fine, they are not differ

Re: Relax test requirements to accomodate fuzz of msacm

2005-02-26 Thread Robert Reif
Jeremy White wrote: So the only fix I can imagine would be to not use msacm to perform these conversions and have a parallel set of converters do this in an aligned fashion. I just tried msacm.drv from a windows 95 CD and it didn't work. I also tried msacm32.drv from xp and it also doesn't work. I

Crash in Polar Precision Performance Software

2005-02-26 Thread Ron Jensen
Hello, This trace is from Polar's Precision Performance Software http://www.codeweavers.com/site/compatibility/browse/name?app_id=681 running on CVS wine. This crash happens with CVS wine, and wine I compiled from http://ftp.codeweavers.com/pub/crossover/office/source/office-src-4.1.0.tgz It doe

Re: MSVCRT: Generating relay stubs for libc forwards/varargs

2005-02-26 Thread Jon Griffiths
Hi Uwe, >I think it would be helpfull, if we could generate debug stubs for >these functions. Can anybody help? If you have the SDK headers, winedump in spec mode can generate this for you. Cheers, Jon = "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste

Re: MSVCRT: Generating relay stubs for libc forwards/varargs

2005-02-26 Thread Uwe Bonnes
> "Jon" == Jon Griffiths <[EMAIL PROTECTED]> writes: Jon> Hi Uwe, >> I think it would be helpfull, if we could generate debug stubs for >> these functions. Can anybody help? Jon> If you have the SDK headers, winedump in spec mode can generate Jon> this for you. For the va

Re: Problem using winelib to compile Std Lib strings

2005-02-26 Thread Jon Griffiths
Hi Rob, >I get a few errors like the following: >error: ::div has not been declared >error: ::ldiv has not been declared div and ldiv may or may not be included in the std namespace. Try changing the calls to either remove the scope resolution from their calls or adding std before it. >And tons

Re: Relax test requirements to accomodate fuzz of msacm

2005-02-26 Thread Robert Reif
Jeremy White wrote: So the only fix I can imagine would be to not use msacm to perform these conversions and have a parallel set of converters do this in an aligned fashion. This would probably be the best way for wine. Keep the existing wave mapper code and just add a better converter specificall

Re: New uninstaller

2005-02-26 Thread Jonathan Ernst
Le samedi 26 fÃvrier 2005 Ã 12:09 +0800, Dmitry Timoshkov a Ãcrit : [...] > > 3) Stringtables > > a)Is there a way to load localized strings without having to guess > > beforehand the size of the string in each language ? > > b)Is there a way to not call LoadString for each string ? > > c)Where is

Re: vartest.c - major pain in the build process

2005-02-26 Thread Mike Hearn
On Sat, 26 Feb 2005 15:56:56 +0100, Marcus Meissner wrote: > well, 25 minutes for a single file and 25 minutes for the rest of the tree? :) It doesn't take 25 minutes here, how much memory do you have? It takes more like 5, which is still excessive :( I disable winetest in my tree entirely, and h

Re: vartest.c - major pain in the build process

2005-02-26 Thread Marcus Meissner
On Sat, Feb 26, 2005 at 10:32:11PM +0800, Dmitry Timoshkov wrote: > "Krzysztof Foltman" <[EMAIL PROTECTED]> wrote: > > > Is there any reason for gcc 3.3.1 to spend several minutes on compiling > > dlls/oleaut32/tests/vartest.c ? > > > > I guess it can be explained by optimization stage going nut

Re: vartest.c - major pain in the build process

2005-02-26 Thread Dmitry Timoshkov
"Krzysztof Foltman" <[EMAIL PROTECTED]> wrote: > Is there any reason for gcc 3.3.1 to spend several minutes on compiling > dlls/oleaut32/tests/vartest.c ? > > I guess it can be explained by optimization stage going nuts on > compiling long functions with many branches (contained in the macros),

Re: Relax test requirements to accomodate fuzz of msacm

2005-02-26 Thread Jeremy White
Robert Reif wrote: Jeremy White wrote: Robert has persuaded me that msacm on Windows does make 'fuzzy' conversions; an 8,000 byte buffer is up sampled to a 47,992 byte buffer instead of the logical (and correct seeming) 48,000 byte buffer. This means that when we go to get the position after play

Re: New uninstaller

2005-02-26 Thread Jonathan Ernst
Le samedi 26 fÃvrier 2005 Ã 09:49 +0900, Mike McCormack a Ãcrit : [...] > Cool. Some comments: > > The dialog box procedure should not handle WM_PAINT or WM_CLOSE, so just > delete those cases from the switch statement. > Ok I did it, but the listbox should be updated when the user ask to unins

vartest.c - major pain in the build process

2005-02-26 Thread Krzysztof Foltman
Is there any reason for gcc 3.3.1 to spend several minutes on compiling dlls/oleaut32/tests/vartest.c ? I guess it can be explained by optimization stage going nuts on compiling long functions with many branches (contained in the macros), but there must be a way to speed this up. It's barely t

Re: Relax test requirements to accomodate fuzz of msacm

2005-02-26 Thread Robert Reif
Jeremy White wrote: Robert has persuaded me that msacm on Windows does make 'fuzzy' conversions; an 8,000 byte buffer is up sampled to a 47,992 byte buffer instead of the logical (and correct seeming) 48,000 byte buffer. This means that when we go to get the position after playing the answer come

Re: USER32: GetScrollBarInfo

2005-02-26 Thread Vitaly Lipatov
В сообщении от 26 Февраль 2005 01:42 Alexandre Julliard написал(a): > Vitaly Lipatov <[EMAIL PROTECTED]> writes: > > +static BOOL SCROLL_GetScrollBarInfo(HWND hwnd, LONG idObject, > > LPSCROLLBARINFO psbi) +{ > > +RECT rect; > > +INT arrowSize, thumbSize, thumbPos, nBar, vertical; > > +