public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: run.exe fails to start XWin on Windows 8.1 through the shortcut
Date: Wed, 12 Aug 2015 20:58:00 -0000	[thread overview]
Message-ID: <87zj1w8hcy.fsf@Rainer.invalid> (raw)
In-Reply-To: <55CB5887.2050607@dronecode.org.uk> (Jon TURNEY's message of	"Wed, 12 Aug 2015 15:30:31 +0100")

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

  reply	other threads:[~2015-08-12 20:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 12:43 Jaakov Jaakov
2015-08-12 14:30 ` Jon TURNEY
2015-08-12 20:58   ` Achim Gratz [this message]
2015-08-13 10:10     ` Jon TURNEY
2015-08-13 17:57       ` Achim Gratz
2015-08-18 15:33   ` Jon TURNEY
2015-08-12 18:11 ` Achim Gratz
2015-08-13 20:11 ` Achim Gratz
     [not found] <1439479795.100500.ezmlm@cygwin.com>
2015-08-13 16:01 ` Jaakov
2015-08-14 20:15 Jaakov Jaakov
2015-08-15  6:40 ` Achim Gratz
2015-08-15 14:07 Jaakov Jaakov
2015-08-15 15:25 ` Achim Gratz
2015-08-15 15:44   ` Marco Atzeri
2015-08-15 16:41 Jaakov Jaakov
2015-08-15 19:08 ` Achim Gratz

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=87zj1w8hcy.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@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).