Re: [coLinux-users] Colinux Blue Screen Crashes

[Henry N. <hen...@ar...>]

Hello Bob,

Bob Wheater wrote:
> Henry N. wrote:
>> But this bug is very difficult to find, because the memory corruption
>> was detected outside of coLinux. It would help more, if you would
>> have a stack trace with module "linux" inside.
>>
>> Henry N.
>
> I checked my 15 crash dumps and none of them have “linux” in the STACK
> TEXT section.  Can you suggest what I can do to capture the stack
> information that you need to help you solve this crash problem.  The
> problem is currently holding up the next release of Portable Ubuntu. 
> Thanks.
>
> Regards,
>
> Bob Wheater
>

No, you can nothing do with the dump or debugger.
Assumed, coLinux ndis-driver will corrupt the memory of an other
process, then very different task will see this, if they use the memory
later.

What you can do is to check that the ndis-driver is truly the problem.
If you installs WinPcap and changes the coLinux config from ndis-bridge
into pcap-bridge. Disappears this the problem?

An other candidate for memory leakages is the option "setcobd=async". It
also crashes without this?

Can you give a command example for console to force this bug on other
distributions? For example running "netio" under Debian 6.0 Squeeze

I see, that you have only 384 MB for the virtual machine. Comes the
crash faster, if you use less memory (for example 256)? Maybe it is a
generally problem with memory.

-- 
Henry N.