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, us
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
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
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
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#Blofe
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 lon
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"
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
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
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 U
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
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 se
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 initali
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
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, t
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
16 matches
Mail list logo
