Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jaakov Jaakov]

Hi Achim:

Regarding run 1.3.3-1, if the command 
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
is issued from the Windows command shell cmd, then C:\cygwin64\run.exe.stackdump is either not generated or not reproducibly generated (it happened just once in a long row of attempts). 
According to the Task Manager, the run process shortly appears and then disappears in one-two seconds. No other effects, except some disc activity, are visible. (In particular, XWin doesn't start.)
\var\log\xwin remains untouched.

Jaakov.

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Achim Gratz]

Jaakov Jaakov writes:
> Regarding run 1.3.3-1,

Is there any reason why you're still bothering with 1.3.3 and not trying 1.3.4?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Marco Atzeri]

On 15/08/2015 17:25, Achim Gratz wrote:
> Jaakov Jaakov writes:
>> Regarding run 1.3.3-1,
>
> Is there any reason why you're still bothering with 1.3.3 and not trying 1.3.4?
>
>
> Regards,
> Achim.

May be as 1.3.4 is test and 1.3.3 is current ?

Regards
Marco




--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jon TURNEY]

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

On 12/08/2015 15:30, Jon TURNEY wrote:
> On 12/08/2015 13:43, Jaakov Jaakov wrote:
[...]
>> The file C:\cygwin64\run.exe.stackdump is generated, containing
>> Stack trace:
> [...]
>
> mumble mumble abracadabra!

Just for the record, the primitive technology which is clearly 
distinguishable from magic, used to produce this backtrace from the 
stackdump, is the attached script.



[-- Attachment #2: stackdump2backtrace --]
[-- Type: text/plain, Size: 458 bytes --]

#!/bin/bash
STACKDUMP=$1
DBG1=/usr/lib/debug/usr/bin/cygwin1.dbg
DBG2=/usr/lib/debug/usr/bin/${STACKDUMP%.stackdump}.exe.dbg

awk '/^[0-9]/{print $2}' $STACKDUMP | while read addr
do
   output=`addr2line -asfiC -e $DBG1 $addr`
   echo $output | fgrep -q "??:0"
   if [ $? -eq 0 ] ; then
     output=`addr2line -asfiC -e $DBG2 $addr`
   fi

   IFS=$'\n' split=($output)
   echo ${split[0]} "|" ${split[length-2]} "|" ${split[length-1]}
done | column -t -s'|'

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Achim Gratz]

Jaakov Jaakov writes:
> Several minites ago I've tried run 1.3.4-1. (Previously, I expected
> getting and using a test version to be much harder than it actually
> turned out to be.)

OK, that explains it.

> And, voilà, starting XWin from the shortcut
> succeeded. Also starting from mintty and cmd. Said that:
> - huge,
> - tremendous,
> - enourmous, - exorbitant
> THANKS to you both, for finding a bug and correcting it.

Well, thanks for reporting the bug with enough information to hunt it
down, since I couldn't reproduce it at all.  And of course to Jon for
saving me the trouble of converting the stackdump back to something that
makes sense and having a good eye on where the actual reason for the
crash might be.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jaakov Jaakov]

> Jaakov Jaakov writes:
> > Regarding run 1.3.3-1,
> Is there any reason why you're still bothering with 1.3.3 and not trying 1.3.4?

Hi Achim and Jon:

Several minites ago I've tried run 1.3.4-1. (Previously, I expected getting and using a test version to be much harder than it actually turned out to be.) And, voilà, starting XWin from the shortcut succeeded. Also starting from mintty and cmd. Said that:
- huge,
- tremendous,
- enourmous, 
- exorbitant
THANKS 
to you both, for finding a bug and correcting it.

Best regards,
Jaakov.
--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Achim Gratz]

Jaakov Jaakov writes:
> 1) Issuing
> C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
> from cmd does not start an Xwin server; no error message is produced.

You don't get a stackdump?

> 2) Issuing run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
> from cygwin64 text console (mintty with some arguments) does start an
> Xwin Server. (Xterm has to be started separately afterwards, but let's
> hope that this is a different issue.)

It is.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jaakov Jaakov]

Achim,

let's hope that your update helps. In the meantime, using run version 1.3.3-1:
1) Issuing
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
from cmd does not start an Xwin server; no error message is produced.
2) Issuing 
run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
from cygwin64 text console (mintty with some arguments) does start an Xwin Server. (Xterm has to be started separately afterwards, but let's hope that this is a different issue.)

Best,
Jaakov.
--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Achim Gratz]

Jaakov Jaakov writes:
> run.exe has version 1.3.3-1.

I've put a test version (run-1.3.4-1) up with these changes:

	* src/util.c (run2_quote_strdup): When quoting, do not simply skip
	empty arguments but return '""'.

	* src/run.c (file_exists_multi): Hoist char* t out of loop and
	initialize NULL.  Remove redundant truncation of fullname.

	* src/run.c (xemacs_special): Replace stricmp with strcasecmp throughout.
	* src/util.c (run2_ends_with): Ditto.

	* src/run.c (parse_args): Implement -wait/--wait and
	-quote/--quote as valid long options, we prefer the double-dash
	variant.
	* src/run.1.in: All long options are preferedly using leading
	double dashes.  Document the fact that single slashes work on two
	of them for backwards compatibility.

Please try it when it becomes available on your mirror and report back
if it fixes your problem.  Thanks.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Achim Gratz]

Jon TURNEY writes:
> There is no implicit initialization of automatic local variables in
> the C language.

Right.  I shouldn't try to reason about code when the temperature is
above 30°C…  :-P


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jaakov]

> Jaakov Jaakov writes:
>> >XWin fails to start again (previously reported half a year ago or so).
>> >
>> >The command issued by a shortcut is
>> >C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
> Can you reproduce this when running the same command from cmd or
> mintty?  If yes, could you run it in a debugger?
>
Thank you, Achim & Jon.

I'll try issuing this command from cmd as soon as possible (in a few 
days, hopefully, I'll get to the machine in question again) and report 
here. I won't be able to use a debugger unless given precise 
instructions. I'm unsure about know what mintty is (Cygwin64 text 
console?), but, if I find it out, I'll also start it from mintty.

Jon is right: the initial value of t is indeterminate according to the C 
standard. The compilers may (and usually will) produce an arbitrarily 
weird code consistent with this semantics.

Best,

Jaakov

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jon TURNEY]

On 12/08/2015 19:57, Achim Gratz wrote:
> Jon TURNEY writes:
>> Not sure if this is the cause of this problem, but after a bit of
>> staring at file_exists_multi(), I notice that run2_fileExits() doesn't
>> initialize t when it returns FALSE, so perhaps the following is a good
>> idea?
>
> The only way I can see this happening is when the initialisation of t
> gets hoisted out of the loop, and if the compiler thinks that is OK to
> do it should not matter if the initializer is an explicit NULL or
> implicit 0.

There is no implicit initialization of automatic local variables in the 
C language.

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Achim Gratz]

Jon TURNEY writes:
> Not sure if this is the cause of this problem, but after a bit of
> staring at file_exists_multi(), I notice that run2_fileExits() doesn't
> initialize t when it returns FALSE, so perhaps the following is a good
> idea?

The only way I can see this happening is when the initalisation of t
gets hoisted out of the loop, and if the compiler thinks that is OK to
do it should not matter if the initializer is an explicit NULL or
implicit 0.  Even if the initializer gets hoisted, the loop never enters
with t non-NULL unless some truly horrible optimization is going on.

But it seems that there are different types in the call vs. the
signature, C string vs. ustr, so where does run get the ustr_*
definitions from on Cygwin?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Achim Gratz]

Jaakov Jaakov writes:
> XWin fails to start again (previously reported half a year ago or so).
>
> The command issued by a shortcut is
> C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"

Can you reproduce this when running the same command from cmd or
mintty?  If yes, could you run it in a debugger?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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

Re: run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jon TURNEY]

On 12/08/2015 13:43, Jaakov Jaakov wrote:
>
> XWin fails to start again (previously reported half a year ago or so).

Thanks for following up on this.

> The command issued by a shortcut is
> C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd;
> /usr/bin/startxwin"
> Upon starting the shortcut, there is some disc acitivty, but no window
> opens, and no XWin processes show up (according to the later-called Task
> Manager).
> No files in the directory /var/log/xwin are updated.
> The file C:\cygwin64\run.exe.stackdump is generated, containing
> Stack trace:
[...]

mumble mumble abracadabra!

> 0x000000018007256a    signal_exit                                                     exceptions.cc:1358
> 0x0000000180073d33    _cygtls::call_signal_handler()                                  exceptions.cc:1828
> 0x000000018012dfef    sig_send(_pinfo*, siginfo_t&, _cygtls*)                         sigproc.cc:714
> 0x000000018012ad90    _pinfo::kill(siginfo_t&)                                        signal.cc:252
> 0x000000018012b259    kill0                                                           signal.cc:303
> 0x000000018012b42c    raise                                                           signal.cc:289
> 0x000000018012b6ef    abort                                                           signal.cc:376
> 0x00000001801612da    dlfree                                                          malloc.cc:4717
> 0x00000001800cd933    free                                                            sync.h:36
> 0x0000000180126d5b    ??                                                              sigfe.s:43
> 0x00000001004011cc    file_exists_multi                                               run.c:877
> 0x0000000100404da8    main                                                            run.c:300
> 0x0000000180048410    dll_crt0_1(void*)                                               dcrt0.cc:1047
> 0x00000001800460dc    _cygtls::call2(unsigned int (*)(void*, void*), void*, void*)    cygtls.cc:112
> 0x0000000180046174    _cygtls::call(unsigned int (*)(void*, void*), void*)            cygtls.cc:30
> 0x00000001004036d1    cygwin_crt0                                                     cygwin_crt0.c:22

Achim,

Not sure if this is the cause of this problem, but after a bit of 
staring at file_exists_multi(), I notice that run2_fileExits() doesn't 
initialize t when it returns FALSE, so perhaps the following is a good idea?

> diff --git a/src/run.c b/src/run.c
> index e88441b..0985571 100644
> --- a/src/run.c
> +++ b/src/run.c
> @@ -880,7 +880,7 @@ file_exists_multi(char* fullname, const char* path,
>      fullname[0] = '\0';
>      for (i = 0; i < extcnt; i++)
>      {
> -        char* t;
> +        char* t = NULL;
>          strcpy(tryName,name_noext);
>          strcat(tryName,exts[i]);
>          if ((run2_fileExists(&t, path, tryName) == TRUE) && t && *t)


-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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

run.exe fails to start XWin on Windows 8.1 through the shortcut

[Jaakov Jaakov]

XWin fails to start again (previously reported half a year ago or so).

The command issued by a shortcut is
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
Upon starting the shortcut, there is some disc acitivty, but no window opens, and no XWin processes show up (according to the later-called Task Manager).
No files in the directory /var/log/xwin are updated.
The file C:\cygwin64\run.exe.stackdump is generated, containing
Stack trace:
Frame         Function     Args
00000235490   0018007256A (0000023E3F4, 00000000000, 00000000000, 0000023DE50)
00000235530   00180073D33 (00000000064, 00000000000, 00000000194, 00000000000)
00000235780   0018012DFEF (0018006BBC3, 000002358E0, 00000000000, 00000000030)
00000235A70   0018012AD90 (0018004339D, 1D0D4F100000000, 00000000000, 00000080000)
00000235C08   0018012B259 (0018014CA5F, 006000180E8, 0018014C94F, 00000000006)
00000235C08   0018012B42C (00600041200, 00600041200, 00600041200, 00000000000)
00000235C08   0018012B6EF (00600041200, 00000000000, 00000235C10, 00000235C10)
00000235C08   001801612DA (00000000104, 00002080064, 00100406000, 00000235C10)
00000235C08   001800CD933 (7FF892714196, 00000000025, 10400000064, 00000000000)
00000235C08   00180126D5B (7FF892714196, 00000000025, 10400000064, 00000000000)
00000235C08   001004011CC (00000000004, 001004070F4, 7FF895624F07, 00000280000)
00600041140   00100404DA8 (00000000000, 0000023CBC0, 00000000000, 00000000001)
0000023CBC0   00180048410 (7FF8909A0000, 0000028ADC0, 7FF5FFFFD001, 7FF800120010)
00000000000   001800460DC (7FF890BC17E9, 00000000000, 7FF8909A13F0, 7FF890BE9FB8)
00000000000   00180046174 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000   001004036D1 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace (more stack frames may be present)

run.exe has version 1.3.3-1.
The output of cygcheck doesn't pass the spam check and can be sent privately.
--
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