Possible bug in Wine or NDISWRAPPER

[gslink]

Francois Gouget wrote:
> On Tue, 11 Jul 2006, gslink wrote:
> 
>> The most common problem with Ndiswrapper is that it requires more than 
>> a 4k stack.  The result you are getting may be coming from a stack 
>> overflow caused by a combination of Wine and Ndiswrapper.
> 
> 
> The 4k stack issue you are talking about is a kernel stack. Wine is a 
> user space application so anything Wine does with its stacks will have 
> no impact on the kernel stack.
> 
> Now it is possible that Wine makes system calls that cause the kernel to 
> recurse and blow its stack, but these calls could just as well happen in 
> any run-of-the-mill Linux application. And in any case, this would be a 
> kernel bug.
> 
> 
What you say is correct but the result is the same.  The combination of 
NDISWRAPPER and any other program fails.  In this case it is Wine.  This 
is not the fault of Wine in any way but it happens.  It is a good idea 
to keep this behavior in mind as NDISWRAPPER is not the only program 
that uses too much stack under some conditions and blows Wine.