I think this may be going slow since the "right people" are not experiencing
this problem, and are therefore unable to try to fix it.
I'm still looking into it, since I have at least a minimal amount of
experience toying with winedbg and my wine exhibits the problem, but of
course I am a bit ou
Mike Hearn <[EMAIL PROTECTED]> writes:
> Hmm, two things. Have I missed anything? Maybe the clipboard server
> thing could be integrated with it, but modern desktops cache X
> selections anyway (or will do soon) so I'm not even sure that's still
> needed. Do we really need a new program for only t
Mike Hearn <[EMAIL PROTECTED]> writes:
> OK. For future reference, what did I do wrong? The styles stuff seems
> rather convoluted.
Well, mostly it was needlessly complicated, and the check for
WS_CAPTION was wrong (WS_CAPTION is not a single bit so you can't test
it with a simple mask).
--
Ale
On Friday 05 December 2003 04:15 pm, Chris Morgan wrote:
> I can see about making this change as I did it once before
> for the jack audio driver.
>
> Can someone fix the debug symbols issue? I've got a patch
> for the jack driver that I'm having trouble debugging
> without it :-P
I think this ma
Le ven 05/12/2003 à 17:05, Bill Medland a écrit :
> (Having just been caught by this again !!)
>
> It would be nice if in the distributions we dynamically detected libartsc and
> libsane rather than requiring them. When someone is installing on a small
> computer they will tend to exclude irrel
I can see about making this change as I did it once before
for the jack audio driver.
Can someone fix the debug symbols issue? I've got a patch
for the jack driver that I'm having trouble debugging
without it :-P
Chris
On Fri, 5 Dec 2003 14:05:13 -0800
Bill Medland <[EMAIL PROTECTED]> wro
(Having just been caught by this again !!)
It would be nice if in the distributions we dynamically detected libartsc and
libsane rather than requiring them. When someone is installing on a small
computer they will tend to exclude irrelevant packages like scanner and sound
software when they do
Robert Shearman wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Alexandre Julliard
Sent: 05 December 2003 03:41
To: Andrew de Quincey
Cc: 'wine-devel'
Subject: Re: Who maintains the imagehlp dll?
Andrew de Quincey <[EMAIL PROTECTED]> writes:
Now that
Yep that is the problem I was seeing with one program I'm running. And this
patch took care of it. Thanks!
Vitaliy Margolen
Tuesday, December 2, 2003, 13:01:18, Vitaliy Margolen wrote:
> Hi, found a problem with the latest locale changes. When it calls the
> GetLocaleInfoW() function, the attac
On December 5, 2003 12:38 pm, Ferenc Wagner wrote:
> We could also generate a test-by-test 'average', 'worst case'
> or 'best case' mixture out of the (hopefully) several
> submissions, of course.
This is what I was hopping we're gonna do. It doesn't
seem right to pick the first one... We could t
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On December 4, 2003 08:10 pm, Ferenc Wagner wrote:
>
>> 4. Which submission should be the principal one? The first?
>
> Why do we need a principal one in the first place?
That would be the one we show in the first table, which
contains one submiss
On December 4, 2003 08:10 pm, Ferenc Wagner wrote:
> Changes needed at least:
> 1. Windows version detected automatically.
For sure. We have all this info into the results however,
shouldn't be too difficult.
> 2. Tester name and contact (?) included in the results.
Would be nice to have, but I
--- Robert Shearman <[EMAIL PROTECTED]> wrote:
> However, most of it is implemented already in winedbg. It has been a
> long-term plan to gradually move code from winedbg to imagehlp (or
> the new
> and similar debugging DLL, dbghelp). PDB files are also supported in
> winedbg
> (so no investigatio
On Fri, 05 Dec 2003 13:54:02 +, you wrote:
> On Fri, 2003-12-05 at 12:07, Rein Klazes wrote:
> > Not the same thing, even not a lot of X in it. What I did was starting
> > the program; wait for the deadlock messages; start gdb; attach the pid
> > of the single wine thread; get the back trace.
Hi
I have a VB6 program which fails on wine due to the Tab control SSTab
from TabCtl32.ocx as other users have reported too. Should this already
work? Is this part of the work of improving wine for VB programs?
Maybe it's not the tab control itself but one of its parts. I made a trace
and this is
On Fri, 2003-12-05 at 12:07, Rein Klazes wrote:
> Not the same thing, even not a lot of X in it. What I did was starting
> the program; wait for the deadlock messages; start gdb; attach the pid
> of the single wine thread; get the back trace. I hope that is correct.
Well, ideally you'd start wined
On Fri, 05 Dec 2003 11:12:55 +, you wrote:
>
> Certainly a backtrace of the deadlock would be interesting, if it is the
> Xi bug it'll look like this:
>
> #0 0x0f04e044 in sigsuspend () from /lib/libc.so.6
> #1 0x0f17cadc in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0
On Fri, Dec 05, 2003 at 10:45:26AM +, Mike Hearn wrote:
> * Support for it is bad in the free software toolchain (no longer an
> issue)
> * Not as many people know it as C (but even fewer know assembly and we
> use that all over the place)
> * Windows is written in C (it's also written in c++ t
On Fri, 2003-12-05 at 10:05, Rein Klazes wrote:
> On Thu, 4 Dec 2003 15:59:51 -0600, you wrote:
> > Log message:
> > Initialize Xlib threading support to see what it breaks...
There is a known deadlock in libXi:
http://bugs.xfree86.org/show_bug.cgi?id=260
A fix has been committed to XFree CV
On Thu, 2003-12-04 at 20:14, Robert Shearman wrote:
> I belive that it is our lack of proper ThreadingModel support in COM. We
> currently ignore the registry parameter
> HKCU\CLSID\{GUID}\InprocServer32\ThreadingModel. I believe we do that right
> thing in the case of that value being Apartment an
On Thu, 2003-12-04 at 18:20, Andreas Rosenberg wrote:
> What's seems to be a big problem, is the InstallShield Setup Engine
> we are using (like many others).
One obvious solution then is to not use InstallShield. NSIS works quite
well in Wine. If you are shipping a Linux version for a customer,
On Thu, 2003-12-04 at 21:32, Alexandre Julliard wrote:
> That's why it needs to be fixed properly. If you just hide the
> symptoms no one will bother to do the right fix.
Well, there are many areas of Wine where we have code in different
places to Windows, so I don't really agree that this patch i
On Thu, 2003-12-04 at 21:29, Alexandre Julliard wrote:
> Yes, but I'll fix that.
OK. For future reference, what did I do wrong? The styles stuff seems
rather convoluted.
On Thu, 2003-12-04 at 18:39, Robert Shearman wrote:
> > 1. C++ code must be accepted - This is not an area that C is good
> > enough, and in any way I don't know C I am only good in C++
>
> I'm afraid there is little chance of getting C++ code into Wine.
It might be worth revisiting this issue at
On Thu, 4 Dec 2003 15:59:51 -0600, you wrote:
> Log message:
> Initialize Xlib threading support to see what it breaks...
Thanks for the warning!
Just about everything here halts after a few minutes:
| err:ntdll:RtlpWaitForCriticalSection section 0x40380db0 "?" wait timed out in thread
0
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Alexandre Julliard
> Sent: 05 December 2003 03:41
> To: Andrew de Quincey
> Cc: 'wine-devel'
> Subject: Re: Who maintains the imagehlp dll?
>
> Andrew de Quincey <[EMAIL PROTECTED]> writes:
>
> > Now that I
26 matches
Mail list logo
