failed to activate core devices errors

hi, i am trying to start XWin.exe in any of the ways described here: http://x.cygwin.com/docs/ug/using.html and with just XWin.exe and ends in Sementation fault and failed to activate core devices errors. I found several post disscussing this on the web but no solution. Does somebody know?

Re: failed to activate core devices errors

hi, thanks for the reply. Swrast_dri.so didnt seems to be the problem in my case, will try the XMing now. I followed this: http://robust.cs.utep.edu/arch1-wiki/index.php/Setup_Xming_and_Cygwin#Installing_and_Configuring_the_Xming_X_Server and got this: C:\Users\katisssxterm -display localhost:0

winsup/cygwin autoload.cc ChangeLog

CVSROOT:/cvs/uberbaum Module name:winsup Changes by: c...@sourceware.org 2011-02-05 19:38:21 Modified files: cygwin : autoload.cc ChangeLog Log message: * autoload.cc (wsock_init): Properly define WSAStartup function pointer to avoid stack

provide __xpg_strerror_r

Our strerror_r is lousy (it doesn't even match glibc's behavior); see my request to the newlib list. But even if newlib swaps over to a POSIX-compliant strerror_r, I argue that for Linux compatibility (not to mention backwards compatibility with existing programs), we need to continue to provide

Re: provide __xpg_strerror_r

On 02/05/2011 01:28 PM, Christopher Faylor wrote: On Sat, Feb 05, 2011 at 01:04:16PM -0700, Eric Blake wrote: Our strerror_r is lousy (it doesn't even match glibc's behavior); see my request to the newlib list. We really should just implement strerror_r in errno.cc. It doesn't make sense

Re: Cygstart through SSH tunnel

On 02/04/2011 10:00 PM, davej1983 wrote: Hi, I'm fairly new to Cygwin, so this might be a pretty simple question, but so far I haven't had any luck finding an answer so far. I have an SSH server running on a remote computer, that I can log into using cygwin. While logged, if I use cygstart to

Re: Cygstart through SSH tunnel

I would mention that there are usually alternatives, in this case vi, but often graphically oriented programs have command line modes for non-interactive usage and they act sanely in headless mode. Sometimes it is nice to have notepad but I've found that usually vi works fine esp in combination

[ANNOUNCEMENT] Updated: coreutils-8.10-1

An updated package, coreutils-8.10-1 release has been uploaded and will soon reach a mirror near you, leaving coreutils 8.8-1 as previous. NEWS: = This is a new upstream release, with upstream details listed below. If you encounter a regression, please report it here rather than upstream.

Re: sigsegv in compiled cygwin

i found small piece of code that need some comment. from trunk int (*wsastartup) (int, WSADATA *); /* Don't use autoload to load WSAStartup to eliminate recursion. */ wsastartup = (int (*)(int, WSADATA *)) GetProcAddress ((HMODULE) (dll-handle),

Re: Cygstart through SSH tunnel

Thanks for your help, and I will definitely look into Cygwin/X. However, from the way you explained it, I'm not sure if I clearly explained what I was trying to do. I'm not actually trying to get the file to open on my local computer, rather I am trying to get them to open/execute on the remote

Re: sigsegv in compiled cygwin

On Sun, Feb 06, 2011 at 03:12:51AM +0900, jojelino wrote: i found small piece of code that need some comment. from trunk int (*wsastartup) (int, WSADATA *); /* Don't use autoload to load WSAStartup to eliminate recursion. */ wsastartup = (int (*)(int, WSADATA *))

Re: sigsegv in compiled cygwin

Why the typedef? cgf int __stdcall (*wsastartup) (int, WSADATA *); /* Don't use autoload to load WSAStartup to eliminate recursion. */ wsastartup = (int __stdcall (*)(int, WSADATA *)) GetProcAddress ((HMODULE) (dll-handle), WSAStartup); adding __stdcall to

Re: sigsegv in compiled cygwin

On Sat, Feb 05, 2011 at 02:35:41PM -0500, Christopher Faylor wrote: On Sun, Feb 06, 2011 at 03:12:51AM +0900, jojelino wrote: i found small piece of code that need some comment. from trunk int (*wsastartup) (int, WSADATA *); /* Don't use autoload to load WSAStartup to eliminate

getopt -- just a nit

This is just a small nit that, I suppose, is for the maintainer of 'getopt'. In /usr/share/getopt, resides the file: 'getopt-parse.bash'. Line 9 of that file is: '# ./parse.bash -a par1 'another arg' --c-long 'wow!*\?' -cmore -b very long' which, in a moment of haste, led me to think I

Re: How to run bash shell script in cygwin?

Hi myuser01, On a bash or similar shell, you need to include the location to the executable file in order to execute it. If the executable directory is not in one of your bin folders you can execute it as part of your PATH. try the following: $ pwd $ echo $PATH $ export $PATH=$PATH;`pwd`

Could not load host key: /etc/ssh_host_ecdsa_key

Just loaded a fresh version of Cygwin-1.7 on a new machine and ran ssh-host-config without any problems. However it keeps failing to start up. The log shows: Could not load host key: /etc/ssh_host_ecdsa_key The config file /etc/sshd_config has the lines: #HostKey

Re: Could not load host key: /etc/ssh_host_ecdsa_key

Jeffrey J. Kosowsky wrote at about 21:54:13 -0500 on Saturday, February 5, 2011: Just loaded a fresh version of Cygwin-1.7 on a new machine and ran ssh-host-config without any problems. However it keeps failing to start up. The log shows: Could not load host key:

Updated: coreutils-8.10-1

An updated package, coreutils-8.10-1 release has been uploaded and will soon reach a mirror near you, leaving coreutils 8.8-1 as previous. NEWS: = This is a new upstream release, with upstream details listed below. If you encounter a regression, please report it here rather than upstream.