Charles Wilson wrote:
> Ken Brown wrote:
>> Here's a simple test case, run from an xterm window:
>
> Thanks for the STC. I can reproduce; I'll look into the problem.
Fixed in svn. There were three problems:
1) derefencing a null ptr
2) some syntax/format issues that arise only when -DUSTR_DEBUG
3) your test.xml file has a bug: xterm.exe doesn't like '-d'.
<X11>
<Environment>
</Environment>
<Target filename="/usr/bin/xterm.exe" startin="~">
- <Arg>-d 127.0.0.1:0.0</Arg>
+ <Arg>-display 127.0.0.1:0.0</Arg>
</Target>
</X11>
Also, minor note: you need to somehow tell run2 where to "look" for the
xserver. Either (a) set $DISPLAY before invoking run2, or (b) specify
it in SelfOptions:
<SelfOptions>
<Arg>-d 127.0.0.1:0.0</Arg>
</SelfOptions>
There's one remaining problem with your scenario: when the Xserver is
not available, and the <GDI> option is used:
<GDI>
<Environment>
</Environment>
<Target filename="/usr/bin/mintty.exe" startin="~">
<Arg>-e /bin/bash</Arg>
</Target>
</GDI>
mintty *IS* launched: it shows up in the process list, but the window is
not visible. I'm not sure why.
--
Chuck
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
