Re: -nolisten tcp -multiwindow combination crashes in XWin startup
Jon TURNEY <jon.turney <at> dronecode.org.uk>
2011-11-01 13:52:25 GMT
On 31/10/2011 19:22, Dave wrote:
> Sadly this one wants to play a little hard to get...
> I have tried this on two somewhat similar machines - 5 years difference in hardware, but both XP Pro
up-to-date on Microsoft Update, and both running the cygwin versions present on mirror.mcs.anl.gov as
of this weekend - both were upgraded, then after both were, I checked that there were no further upgrades
posted in between. The two differ regarding which packages are present, but for those present, they'd
seem to be at the same versions.
> One shows this problem quite consistently, the other doesn't show it at all. It's the newer one, which has a
good amount of memory to spare and is usually the more reliable these days, that is showing the problem.
> I can recreate the problem at will on the one that shows it by starting XWin at the command line directly,
under xinit, or under startxwin. But if I try to start XWin under gdb, I don't see the problem; see below.
(The page you pointed me to suggests attaching gdb after startup, but that doesn't seem reasonable in this case.)
> I notice in the output from starting XWin at the command line there's the line
> 3 [main] XWin 4520 fork: child 5408 - died waiting for dll loading, errno 11
> I didn't see this output or captured in /var/log/xwin/XWin.0.log when I ran via xinit or startxwin. I
don't know if that line got generated but lost in output redirections, or if this way of starting X is maybe
seeing yet a different problem. This line seems similar to that reported by Denis Beauchemin, Wed, 19 Oct
2011 14:17:54 +0000.
Yes, this line is output directly by the cygwin DLL, so you won't see it in
This output is typical of some other software causing cygwin problems with
fork emulation, see  and  in the FAQ.
> Any suggestions re how else to get the backtrace you desire, or any other info that might be helpful?