Mounir IDRASSI [EMAIL PROTECTED] wrote:
diff --git a/include/scarderr.h b/include/scarderr.h
new file mode 100755
index 000..c07833e
--- /dev/null
+++ b/include/scarderr.h
...
diff --git a/include/winscard.h b/include/winscard.h
new file mode 100755
index 000..f302a9f
--- /dev/null
Sorry, my mistake... I'll definitely be more careful next time.
Mounir IDRASSI
IDRIX - Cryptography and IT Security Experts
http://www.idrix.fr
Dmitry Timoshkov wrote:
This is a notice more for Alexandre this time, but next time please
make sure to send the files with exec bits turned off (755
Tom Spear [EMAIL PROTECTED] writes:
Haven't killed it yet and been waiting for 2 hours.. I'm on a T-3
afaik. Last line that prints before it just sits is:
walk 4eea356e2d39f1a958afb4d8f5b54381e8972ecf
This turns out to be a bug in libcurl. It's fixed in libcurl = 7.16.
--
Alexandre
On 5/2/07, Alexandre Julliard [EMAIL PROTECTED] wrote:
Tom Spear [EMAIL PROTECTED] writes:
Haven't killed it yet and been waiting for 2 hours.. I'm on a T-3
afaik. Last line that prints before it just sits is:
walk 4eea356e2d39f1a958afb4d8f5b54381e8972ecf
This turns out to be a bug in
Just curious if there was something wrong with the regedit patch I
sent on Friday, or if maybe there is a particular reason that the /C
was left out of the code in the first place, that I am missing, and
would help me to understand.
On 5/2/07, Tom Spear [EMAIL PROTECTED] wrote:
On 5/2/07, Alexandre Julliard [EMAIL PROTECTED] wrote:
Tom Spear [EMAIL PROTECTED] writes:
Haven't killed it yet and been waiting for 2 hours.. I'm on a T-3
afaik. Last line that prints before it just sits is:
walk
Mounir IDRASSI a écrit :
Should we fill a bugzilla report before submitting the patch?
Thanks.
no need for opening the bugzilla entry, just send the patch to wine-patches
A+
--
Eric Pouech
The problem with designing something completely foolproof is to underestimate the
ingenuity of a
Markus Amsler a écrit :
I've played around with dbghelp performance. My test case was breaking
at an unknown symbol (break gaga) while WoW was loaded in the debugger
(wine winedbg WoW.exe). The time was hand stopped, memory usage
measured with ps -AF and looked at the RSS column.
Test
+for(i = 0; i 16 /* Max vertex attribs */; i++) {
I think you should be using MAX_ATTRIBS there.
Changing the strided data like that in drawPrimitive looks rather hacky to me.
Does anyone know where a call to OLE2A is going to enter wine?
Presumably OLE2A returning null means that the thread ran out of stack
space?
Bill Medland
Eric Pouech wrote:
Markus Amsler a écrit :
I've played around with dbghelp performance. My test case was
breaking at an unknown symbol (break gaga) while WoW was loaded in
the debugger (wine winedbg WoW.exe). The time was hand stopped,
memory usage measured with ps -AF and looked at the RSS
H. Verbeet wrote:
+for(i = 0; i 16 /* Max vertex attribs */; i++) {
I think you should be using MAX_ATTRIBS there.
Changing the strided data like that in drawPrimitive looks rather
hacky to me.
You cannot access the strided data by both named approach
(u.s.something) and
On 5/2/07, Scott Ritchie [EMAIL PROTECTED] wrote:
In the (distant) future, will we support building Wine with both 64 bit
and 32 bit libraries, and then the same Wine installation will run both
64 bit and 32 bit apps? As I understand it, this is the way Windows
does in its 64 bit versions.
I
On Wed, 2007-05-02 at 21:54 -0400, Steven Edwards wrote:
On 5/2/07, Scott Ritchie [EMAIL PROTECTED] wrote:
In the (distant) future, will we support building Wine with both 64 bit
and 32 bit libraries, and then the same Wine installation will run both
64 bit and 32 bit apps? As I understand
On Wed, May 02, 2007 at 03:32:59PM -0700, Bill Medland wrote:
Does anyone know where a call to OLE2A is going to enter wine?
Presumably OLE2A returning null means that the thread ran out of stack
space?
What is OLE2A? I do not see it mentioned anyewhere in the Wine source.
Any more debugging
15 matches
Mail list logo
