Frédéric L. W. Meunier wrote:
> I was running devel-20070423 for 35 days and got it while
> running two instances of a lynx -dump in a loop.
>
> Faulting application colinux-slirp-net-daemon.exe, version
> 0.8.0.0, faulting module colinux-slirp-net-daemon.exe, version
> 0.8.0.0, fault address 0x00006180.
>
> I don't know if the address gives any information, but that's
> all I got.
>
> I'm now running 20070511.
>
> When it crashes, do you really have to restart coLinux ?
No.
You can view the comamnd line from a running
colinux-slirp-net-daemon.exe and simple restart it from a windows
command line with same parameters for this colinux session.
ProcessExplorer from www.sysinternals.com let you show the parameters of
a running process.
I will check what the address can see. But I'm afraid, the address not
helps.
If you can, you would help with a debugging run of slip:
o Download the gdb.exe from mingw32 project (not CygWin!)
o Download the debugging version of colinux (file
daemons-0.8.0-20070511.dbg.zip)
o Replace the colinux-slirp-net-daemon.exe from this zip
o Start colinux
o Copy & paste current args of running colinux-slirp-net-daemon somether
o Terminate/Kill the colinux-slirp-net-daemon
o Restart colinux-slirp-net-daemon.exe from gdb.exe, paste the args in
the parameter list for gdb
o Wait for your crash ;-)
o View the 'backtrace' from stack. The caller chain is interesting and
what function was crashing.
--
Henry
|
