The previous version, that was stable for xorg-server was 1.8.2-1,
according to setup.log.
The gdb stack trace is not very talkative:
...
Loaded symbols for /usr/bin/cygXrender-1.dll
[Switching to thread 8788.0x2740]
(gdb) c
Continuing.
(no debugging symbols found)
Program received signal SIGSEGV
Dear Jon,
Since the update I have been unable to start XWin under [1.7].
Following my usual sequence at a bash prompt:
mount n:/tmp /tmp # drive n: is NTFS as required
run XWin -multiwindow &
Normally these two would be followed by a command line for xterm, but I
am not getting that far! The s
of time, I've uploaded an unstripped build at [1]
[1] ftp://cygwin.com/pub/cygwinx/XWin.20101108-git-eb4deaf9bfbab023.exe.bz2
> Something funny about it:
> I had the "xset fp+ tcp/mystique:7100" commented out in the
> .startxwinrc.
> Then I started XWin, attached the gd
On 08/11/2010 11:48, Fergus wrote:
> Since the update I have been unable to start XWin under [1.7].
> Following my usual sequence at a bash prompt:
>
> mount n:/tmp /tmp # drive n: is NTFS as required
> run XWin -multiwindow &
>
> Normally these two would be followed by a command line for xterm,
I did a bit of further reseach.
It looks like it does not have anything to do with the way the font server is
queried,
but rather the way the startup is done.
When I have the font server added during the XWin startup - either in the
startxwin.bat, or a bash-script I call from there, the XWin S
On 11/8/2010 6:48 AM, Fergus wrote:
PS It kills me not to copy this to cygwin at cygwin dot com which I feel will
have a much wider readership and skill set amongst that readership, but
anybody sinning in this regard is always referred straight to Cygwin-X.
Because this is where those intereste
