delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/10/03/12:56:34

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <bfc52fe00510030956m1ea87206scfec67228b10511@mail.gmail.com>
Date: Mon, 3 Oct 2005 10:56:24 -0600
From: Aaron Humphrey <alfvaen AT gmail DOT com>
Reply-To: Aaron Humphrey <alfvaen AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygstart regression [Was: Re: on the road to 1.5.19 - snapshot testing needed]
In-Reply-To: <434074CA.7030907@mscha.org>
MIME-Version: 1.0
References: <20050929231320 DOT GA13715 AT trixie DOT casa DOT cgf DOT cx> <bfc52fe00509300817j52549078x90263e13fa9a4f75 AT mail DOT gmail DOT com> <20050930152750 DOT GB13201 AT trixie DOT casa DOT cgf DOT cx> <433D62A7 DOT 7090207 AT cwilson DOT fastmail DOT fm> <434074CA DOT 7030907 AT mscha DOT org>
X-IsSubscribed: yes
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j93GuXne015783

On 10/2/05, Michael Schaap wrote:
> To be able to check whether something has changed in the path handling,
> I've uploaded a version of cygstart that prints out the exact
> ShellExecute call it is making, at
> <http://www.mscha.org/cygstart_dbg.zip>.  Could you perhaps download
> that, try it out both with a snapshot and 1.5.18, and let us know
> whether it prints out something different?

With 20050930 snapshot, running 'cygstart_dbg empty.mdb':

ShellExecute(
    "(null)",
    "(null)",
    "empty.mdb",
    "(null)",
    "(null)",
    1
);

With 1.5.18, the same command:

ShellExecute(
    "(null)",
    "(null)",
    "empty.mdb",
    "(null)",
    "(null)",
    1
);

They look pretty similar to me.

> If that's not it, then I don't know what it could be.  Must have
> something to do with timing, or the exact memory location, or something
> like that, especially since the problem disappears under strace...
> To track it down, perhaps you could try:
>  - "cmd /c start whatever.mdb" from a Cygwin prompt

Works.  So at least this gives me a better workaround than running strace,
if I can remember it.

>  - "cygstart whatever.mdb" from a cmd.exe command prompt

Works.

>  - save the simplest possible Access database, and see if cygstart can
> open that

Doesn't work.

>  - make sure whatever.mdb is on a local disk, in the current directory,
> and has a simple file name

'empty.mdb' is in 'C:\'.  Running 'cygstart empty.mdb' from /cygdrive/c doesn't
work.

For all cases, "works" means that the mdb file comes up properly in Access 97,
whereas "doesn't work" means the error message mentioned in my original
email on the subject(http://cygwin.com/ml/cygwin/2005-09/msg00923.html).

For another data point, cygstart works fine on my Windows 98 SE computer,
running a recent snapshot(forget which one, sorry), but it has Access 2000.

--
--Alfvaen (Web page: http://www.telusplanet.net/public/alfvaen/ )
Current Album--Clannad:Dulaman
Current Book--Michael G. Coney:Friends Come In Boxes
I'm living in a neon house; I'm living in avalanche row; I'm living in
hangover city

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019