On Dec 23, 2011, at 3:10 PM, Michael Ost wrote:
> This all makes sense, and pulls the code together for me. Thanks!
You're welcome.
> I assume this is a recent development, because I was successfully using gdb
> with our last wine version - 1.1.7.
Nope. This is how it has worked for a long,
On Fri, Dec 23, 2011 at 7:11 PM, wrote:
>
> Also, there's one thing that has annoyed me for months. Since one of
> Damjan Jovanovic's patches, my /tmp/ directory gets spammed with .icons
> files, thousands of them after some time. IIRC on Linux, it's always
> the same .desktop files that are re
On 12/22/11 8:20 PM, Ken Thomases wrote:
On Dec 22, 2011, at 8:14 PM, Vitaliy Margolen wrote:
On 12/22/2011 04:45 PM, Michael Ost wrote:
I'm seeing a SEGV crash when running any wine program with wine 1.3.24 in
gdb but not when running without the debugger. The crash is happening when
writing
As I've got no idea of the status of DIB engine, besides looking at changelogs,
I'd like to know it... at least to see if there's some need of help.
The stuff that interests me at most is, as usual, the display speed of
autocad with embedded truetype fonts (aka bug 13801), which depends deeply
on
Hi,
I encourage the Mac OS X users among you to retest your apps.
I have observed several bugs but have not found time to bisect them.
Some of those may be old as I don't have time either to test apps
regularly, i.e. with every release.
o mouse issues (likely shared with XInput 2 trouble on Linu
Akihiro Sagawa writes:
> Fixed build failure. (IsDBCSLeadByte -> IsDBCSLeadByteEx)
> ---
> dlls/gdi32/font.c | 14 +++---
> dlls/gdi32/tests/font.c | 30 +++---
> 2 files changed, 34 insertions(+), 10 deletions(-)
It doesn't work here:
../../../tools/r
On 2011-12-23 12:41:56 +0100, Piotr Caban wrote:
> This is still not working good. I don't know how it should be
> implemented without doing much more testing. Probably printing a
> FIXME message and returning an error will be acceptable.
>
> If you want to fully implement it I guess it should do
On 12/23/11 08:44, Kusanagi Kouichi wrote:
+ if (!buf)
+ {
+_invalid_parameter(NULL, NULL, NULL, 0, 0);
+return 0;
+ }
You should set errno here.
+ if (bufsize / size< count)
+ {
+fread(buf, bufsize, 1, fp);
+if (!feof(fp))
+{
+ _invalid_parameter(NULL, NULL, NUL
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=16144
Your paranoid android
