public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: Issue with XWin under xlaunch
Date: Tue, 24 Apr 2012 13:27:00 -0000	[thread overview]
Message-ID: <4F96A9FF.7090005@cornell.edu> (raw)
In-Reply-To: <4F96946A.4070406@dronecode.org.uk>

On 4/24/2012 7:54 AM, Jon TURNEY wrote:
> On 23/04/2012 16:04, Ken Brown wrote:
>>> I've added some code to capture stdout and stderr from these subprocesses to
>>> the X server log, and to more clearly diagnose problems which could occur
>>> while fork/exec-ing them.
>>
>> Would it be possible for you to also add some code for diagnosing problems with processes started from .startxwinrc?  I'm hoping it might help with the problem I reported in
>>
>>    http://cygwin.com/ml/cygwin-xfree/2012-04/msg00050.html
>
> Hmm.. not sure code is really needed.  You can see the output from startxwin
> by running it from a terminal, or capture it by changing the shortcut which
> runs it to something like the following (perhaps we should do that by default)
>
> C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe
>>> /var/log/xwin/startxwin.log 2>&1'

That doesn't help, but I'll reply to my original thread to explain why. 
  I shouldn't have interjected my question into this thread.

Ken


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2012-04-24 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 10:24 Eliot Moss
2012-04-23 13:51 ` Jon TURNEY
2012-04-23 15:04   ` Ken Brown
2012-04-24 11:54     ` Jon TURNEY
2012-04-24 13:27       ` Ken Brown [this message]
2012-04-23 16:42   ` Eliot Moss
2012-04-23 16:46     ` Eliot Moss
2012-04-24 11:40     ` Jon TURNEY
2012-04-24 12:23       ` Eliot Moss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F96A9FF.7090005@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).