Kirill,
I see what you're getting at. The valgrind error comes about when we call
get_column_info in streams.c. No string is allocated for table_name there,
so the pointer remains uninitialized.
I am unfamiliar with the streams use case, but looking at
tests/db.c:test_streamtable(), I think
> I am using wine 1.1.32, can anyone tell me how to install a windows
> service(say NETBIOS) in wine?
Wrong list, you want wine-users instead.
--Juan
Hi all
I am using wine 1.1.32, can anyone tell me how to install a windows
service(say NETBIOS) in wine?
I saw there is a services.exe running, but I didn't find any document on
winehq saying how to add new wine services.
I appreciate your help
Best Regards
Zhao Wang
Am Tuesday 03 November 2009 23:32:42 schrieb Juan Lang:
> These were too easy to pass up.
> --Juan
+BOOL WINAPI CertAddEncodedCertificateToSystemStoreW(LPCWSTR pszCertStoreName,
+ const BYTE *pbCertEncoded, DWORD cbCertEncoded)
+{
[snip]
+store = CertOpenSystemStoreA(0, pszCertStoreName);
Thi
> + store = CertOpenSystemStoreA(0, pszCertStoreName);
>
> This looks wrong to me ...
To me too :) Thanks!
--Juan
>Or use a goertzel detector for the transmitted tone(s).
>It is also quite simple to generate sine waves without any trig.
Just another, less advanced, idea,
Even easier would making a really slow square wave(~0.5 Hz) that follows a
simple pattern, like 80, 80, 80, -80, -80, -80, 80, 80, 80...fo
On Tue, Nov 3, 2009 at 3:33 PM, wrote:
> Hi,
>
> Eric Pouech wrote:
>>> It is not acceptable that µ-law code bit-rots because of
>>lack of continuous
>>> testing (assuming it worked the day it was checked in).
>
>>actually, you can add a (small) wave file in the test program (and
>>create on the
On Tue, Nov 03, 2009 at 07:48:29PM +0200, Damjan Jovanovic wrote:
> On Tue, Nov 3, 2009 at 3:33 PM, wrote:
> >
> > Wine would benefit from a test in msacm32/tests/ sketched as follows:
> > 0. choose some base frequency like 11025Hz;
> > 1. generate a PCM sine wave tone (like winmm/tests/wave.c);
For what it's worth, here are the valgrind warnings
from a run of my current subset of the chromium test suite
under valgrind+wine:
http://kegel.com/wine/chromium/valgrind-logs/errors.html
Mostly they're leaks. That's good news.
For the few nonleak warnings, I already filed
http://bugs.winehq.o
Hi,
Eric Pouech wrote:
>> It is not acceptable that µ-law code bit-rots because of
>lack of continuous
>> testing (assuming it worked the day it was checked in).
>actually, you can add a (small) wave file in the test program (and
>create on the fly the needed file)
>we already test some .exe th
10 matches
Mail list logo
