Re: run.exe fails to start XWin on Windows 8.1 through the shortcut
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.
#!/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'|'
--
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 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
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
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
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
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
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
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
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
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 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
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
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!
0x00018007256asignal_exit
exceptions.cc:1358
0x000180073d33_cygtls::call_signal_handler()
exceptions.cc:1828
0x00018012dfefsig_send(_pinfo*, siginfo_t, _cygtls*)
sigproc.cc:714
0x00018012ad90_pinfo::kill(siginfo_t)
signal.cc:252
0x00018012b259kill0
signal.cc:303
0x00018012b42craise
signal.cc:289
0x00018012b6efabort
signal.cc:376
0x0001801612dadlfree
malloc.cc:4717
0x0001800cd933free
sync.h:36
0x000180126d5b??
sigfe.s:43
0x0001004011ccfile_exists_multi
run.c:877
0x000100404da8main
run.c:300
0x000180048410dll_crt0_1(void*)
dcrt0.cc:1047
0x0001800460dc_cygtls::call2(unsigned int (*)(void*, void*), void*,
void*)cygtls.cc:112
0x000180046174_cygtls::call(unsigned int (*)(void*, void*), void*)
cygtls.cc:30
0x0001004036d1cygwin_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
Re: run.exe fails to start XWin on Windows 8.1 through the shortcut
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
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 in Windows 8.1
On 01/06/2015 22:38, jaakov jaakov wrote: Finally, I got to the machine that won't start XWin. It is different now: XWin won't start as before, but now no run.exe.stackdump file is produced. The start command is C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c cd; /usr/bin/startxwin Thanks for following up on this. But I'm sorry, there's nothing to go on there. Is it possible for you to upload the output of stracing that run command somewhere? -- 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 in Windows 8.1
You review (and possible upload) the output from this directory: /var/log/xwin You could at least then confirm the xwin application is running, and starting (even if it then crashes)... I had issues after recent upgrades (probably over a year ago) because of what I had in my local .startxwin... I only discovered it by looking at these xwin logs. Gavin -Original Message- From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of Jon TURNEY Sent: 04 June 2015 12:19 To: jaakov jaakov; cygwin@cygwin.com Subject: Re: run.exe fails to start XWin in Windows 8.1 On 01/06/2015 22:38, jaakov jaakov wrote: Finally, I got to the machine that won't start XWin. It is different now: XWin won't start as before, but now no run.exe.stackdump file is produced. The start command is C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c cd; /usr/bin/startxwin Thanks for following up on this. But I'm sorry, there's nothing to go on there. Is it possible for you to upload the output of stracing that run command somewhere? -- 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 in Windows 8.1
On 02/05/2015 20:32, jaakov jaakov wrote: While executing the command Xwin Server from Windows 8.1, the server won't start. Apparently, the executed command is C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c cd; /usr/bin/startxwin The file C:\cygwin64\run.exe.stackdump is produced. Instead I expect, however, an X server process and an xterm window. On the other hand, starting first Cygwin64 terminal does create a text console shell, and running startxwin from this shell does give me an X server process and an xterm window. A complete removal of the C:\cygwin64 directory and reinstalling did not help. Afterwards, reinstalling xinit did not help. This issue persists for a few months already. Last year, XWin started without problems. Unfortunately, the stackdump in your previous report [1] didn't quite contain enough information to investigate this problem. I've made a small improvement in how the stackdumps are made [2] since then, so if you can upgrade and provide the stackdump file, perhaps we can discover why this crash is happening. [1] https://cygwin.com/ml/cygwin/2015-03/msg00117.html [2] https://cygwin.com/ml/cygwin-patches/2015-q1/msg00018.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 in Windows 8.1
While executing the command Xwin Server from Windows 8.1, the server won't start. Apparently, the executed command is C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c cd; /usr/bin/startxwin The file C:\cygwin64\run.exe.stackdump is produced. Instead I expect, however, an X server process and an xterm window. On the other hand, starting first Cygwin64 terminal does create a text console shell, and running startxwin from this shell does give me an X server process and an xterm window. A complete removal of the C:\cygwin64 directory and reinstalling did not help. Afterwards, reinstalling xinit did not help. This issue persists for a few months already. Last year, XWin started without problems. Unfortunately, the stackdump in your previous report [1] didn't quite contain enough information to investigate this problem. I've made a small improvement in how the stackdumps are made [2] since then, so if you can upgrade and provide the stackdump file, perhaps we can discover why this crash is happening. [1] https://cygwin.com/ml/cygwin/2015-03/msg00117.html [2] https://cygwin.com/ml/cygwin-patches/2015-q1/msg00018.html Great, I'll test it as soon as possible! -- 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
