Re: SNsdk on WinNT ?

Re: SNsdk on WinNT ?

[Marta Stojanovic]

>CreateProcess is an NT thing. It is like a fork+exec, it must
>mean that the system can not find a program it wants to run.
>This has nothing to do with TCL_LIBRARY or anything like
>that. You are going to have to debug this one yourself,
>I would say double check that the fully qualified SN bin dir
>is on your PATH. You should just be able to run SN by double
>clicking on the SN program from the Windows Explorer.


I just wanted to clarify : Source Navigator works very well on NT, it
produces all the database files. But I would like to use your Database
API, which I do get running my script with :

SNsdk <script name> ...

Typing "SNsdk" gives me previously mentioned error message. Typing
"hyper" opens Tcl console, but when I go to File - Source .. .and try to
open any Tcl script (from SN examples) it crashes.

Yes, the full path of bin/ directory is in the PATH. It recognizes
"SNsdk" but it doesn't find some files. When I searched for the string
"CreateProcess ... " I found it in all .exe files from the bin
directory. That's why I thought that it has something to do with
environment variables.

I'll keep trying, thanks for any tip you can think of.

Kind regards,
Marta.

Re: SNsdk on WinNT ?

[Ben Elliston]

   Typing "SNsdk" gives me previously mentioned error message. Typing
   "hyper" opens Tcl console, but when I go to File - Source .. .and try
   to open any Tcl script (from SN examples) it crashes.

What was the reason for a separate "SNsdk" (ick) interpreter again?

Ben

Re: SNsdk on WinNT ?

[Syd Polk]

At 09:36 AM 12/14/00 +1100, Ben Elliston wrote:
>    Typing "SNsdk" gives me previously mentioned error message. Typing
>    "hyper" opens Tcl console, but when I go to File - Source .. .and try
>    to open any Tcl script (from SN examples) it crashes.
>
>What was the reason for a separate "SNsdk" (ick) interpreter again?
>
>Ben

Because a pure GUI application has no stdin or stdout.


Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.

Re: SNsdk on WinNT ?

[Ian Roxborough]

Ben Elliston wrote:
> 
>    Typing "SNsdk" gives me previously mentioned error message. Typing
>    "hyper" opens Tcl console, but when I go to File - Source .. .and try
>    to open any Tcl script (from SN examples) it crashes.
> 
> What was the reason for a separate "SNsdk" (ick) interpreter again?

Because of Windows GUI programs can't read or write to std in/out.
SNsdk is a (console) wrapper program for hyper, it grabs/puts standard
in/out and passes it onto hyper (which on Windows is compiled with
WishCon patch to allow stdin/stdout access).

Ian.

Re: SNsdk on WinNT ?

[Marta Stojanovic]

>
> >I wouldn't mind, but it doesn't work for me : do you use File-Source ...
> >from hyper's console ? Or you type  directly the name of the script with
> >it's arguments ? In the first case it crashes immediately after. In the
> >second case it gives me :
> >couldn't execute "my_script.tcl": invalid argument . Any idea why ? It
> >works very well on Linux. For Windows I erased everything from the
> >beginning to the end of the line "exec hyper ..." .
>
> We will be looking at this problem in detail in January. I am sorry this
> won't help you now.

Hi Sid!

Well, I didn't want to wait until January, so I tried to recompile SN on WinNT
using as APPNAME \"hyper.exe\" in Makefile.am. As you can guess, it was not an
easy task (I have MSDEV 6.0, not 5.0) ... there was an error concerning stat.h
(it couldn't find the field st_blksize at "stat" struc from stat.h : that
structure is different in stat.h from MSDEV and from Cygwin). I tried to give
it Cygwin's stat.h, but than time.h didn't work etc. etc.

So, I moved to Makefile.am again, in order to comment everything concerning SN
and to leave only lines for snsdk. Again, problems with compilation : grep.obj,
LNK20001 etc..

Finally (it took me time), I remembered that snsdk is in fact only one file :
winCon.c. So I compiled it under MSDEV 6.0 with -DAPPNAME=\"hyper.exe\" as an
option, and it WORKED FINE ! Well, not that fine in fact : now this new .exe
file executes very well (thanks God!) my Tcl script, but it crashes at the end
(Xavier mentioned that, so I think he did the same thing). When it crashes, the
window with Application Error comes up, and if you click on Cancel to debug it,
another error message appears :

        Unhandled exception in hyper.exe (SNTCL81.DLL). Access violation.


I tried to see whether the error comes from winCon.c code, but it seems to me
that it's an error in hyper's code. Do you have any idea of why this error
takes place ?

Just one more thing : if I don't put "exit" at the end of my Tcl script, it
won't give me that error message, but it will wait for my Ctrl-C to end. Seems
that it doesn't handle that "exit" very well, but again I don't know whether
it's hyper or snsdk. Any idea ?

Thanks.

Kind regards,
Marta.

Re: SNsdk on WinNT ?

[Syd Polk]

At 11:03 AM 12/14/00 -0800, Ian Roxborough wrote:
>Xavier Nodet wrote:
> > BTW, as SNSdk.exe is not intended to be used by
> > Source Navigator itself, it could simply use
> > "hyper.exe" instead of "..\bin\hyper.exe" and
> > ask the user to have hyper.exe in the path...
>
>I can't think why it's hardcoded to "..\bin\hyper.exe".

Because we used to have a libexec directory. It was probably just changed 
to "bin" when we got rid of it.

>
> > And while we're at it, why not directly launching
> > hyper.exe from the command line ? It executes the
> > script as well, for me ! Except that it crashes,
> > but after having finished the script, so...
>
>hyper.exe is read from stdin and writing to stdout
>without any problems and without the wrapper app?
>
>Ian

Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.

Re: SNsdk on WinNT ?

[Syd Polk]

At 02:05 PM 12/14/00 -0500, Marta Stojanovic wrote:
> >
> >
> > With the path to hyper.exe (badly) hardcoded in the exe,
> > I see no other way than to recompile it ;-(
> >
>
>Yes, it occured to me :(
>
>
> >
> > BTW, as SNSdk.exe is not intended to be used by
> > Source Navigator itself, it could simply use
> > "hyper.exe" instead of "..\bin\hyper.exe" and
> > ask the user to have hyper.exe in the path...
> >
>
>Exactly.

This is a problem. One of the best features about SN is that you don't have 
to modify the enviroment to run it. The real solution is to construct the 
path to hyper using Tcl commands. This has to be overhauled for internal 
reasons here at Red Hat anyway.



> >
> > And while we're at it, why not directly launching
> > hyper.exe from the command line ? It executes the
> > script as well, for me ! Except that it crashes,
> > but after having finished the script, so...
>
>I wouldn't mind, but it doesn't work for me : do you use File-Source ...
>from hyper's console ? Or you type  directly the name of the script with
>it's arguments ? In the first case it crashes immediately after. In the
>second case it gives me :
>couldn't execute "my_script.tcl": invalid argument . Any idea why ? It
>works very well on Linux. For Windows I erased everything from the
>beginning to the end of the line "exec hyper ..." .

We will be looking at this problem in detail in January. I am sorry this 
won't help you now.


Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.

Re: SNsdk on WinNT ?

[Ian Roxborough]

Xavier Nodet wrote:
> BTW, as SNSdk.exe is not intended to be used by
> Source Navigator itself, it could simply use
> "hyper.exe" instead of "..\bin\hyper.exe" and
> ask the user to have hyper.exe in the path...

I can't think why it's hardcoded to "..\bin\hyper.exe".
 
> And while we're at it, why not directly launching
> hyper.exe from the command line ? It executes the
> script as well, for me ! Except that it crashes,
> but after having finished the script, so...

hyper.exe is read from stdin and writing to stdout
without any problems and without the wrapper app?

Ian

Re: SNsdk on WinNT ?

[Marta Stojanovic]

>
>
> With the path to hyper.exe (badly) hardcoded in the exe,
> I see no other way than to recompile it ;-(
>

Yes, it occured to me :(


>
> BTW, as SNSdk.exe is not intended to be used by
> Source Navigator itself, it could simply use
> "hyper.exe" instead of "..\bin\hyper.exe" and
> ask the user to have hyper.exe in the path...
>

Exactly.


>
> And while we're at it, why not directly launching
> hyper.exe from the command line ? It executes the
> script as well, for me ! Except that it crashes,
> but after having finished the script, so...

I wouldn't mind, but it doesn't work for me : do you use File-Source ...
from hyper's console ? Or you type  directly the name of the script with
it's arguments ? In the first case it crashes immediately after. In the
second case it gives me :
couldn't execute "my_script.tcl": invalid argument . Any idea why ? It
works very well on Linux. For Windows I erased everything from the
beginning to the end of the line "exec hyper ..." .

Thank you very much.

Kind regards,
Marta.

RE: SNsdk on WinNT ?

[Xavier Nodet]

From: sourcenav-owner@sources.redhat.com
> [ mailto:sourcenav-owner@sources.redhat.com]On Behalf Of 
> Marta Stojanovic
>
> [Interesting stuff]
>
> Am I wrong or cmd should be something like : "hyper.exe 
> <script name>"
> (in this case "hyper.exe toto") ?

I suppose so.

> Maybe I'm completely wrong ... If not, does someone has an 
> idea of how
> to make this thing work without having to change makefile 
> or winCon.c
> and recompile it on WinNT (I prefer ready-made binaries, to 
> tell you the
> truth) ?

With the path to hyper.exe (badly) hardcoded in the exe,
I see no other way than to recompile it ;-(

BTW, as SNSdk.exe is not intended to be used by
Source Navigator itself, it could simply use
"hyper.exe" instead of "..\bin\hyper.exe" and
ask the user to have hyper.exe in the path...

And while we're at it, why not directly launching 
hyper.exe from the command line ? It executes the 
script as well, for me ! Except that it crashes, 
but after having finished the script, so...

-- 
Xavier Nodet

Re: SNsdk on WinNT ?

[Marta Stojanovic]

>
>
> Here is the definition of this function.
>
> CreateProcessA(
>     LPCSTR lpApplicationName,
>     LPSTR lpCommandLine,
>     LPSECURITY_ATTRIBUTES lpProcessAttributes,
>     LPSECURITY_ATTRIBUTES lpThreadAttributes,
>     BOOL bInheritHandles,
>     DWORD dwCreationFlags,
>     LPVOID lpEnvironment,
>     LPCSTR lpCurrentDirectory,
>     LPSTARTUPINFOA lpStartupInfo,
>     LPPROCESS_INFORMATION lpProcessInformation
>     );
>
> I traced snsdk.exe and found the following arguments for
> the first call to this function (it crashes in this function) :
>
> - the return address (next instruction to execute
> after returning from the function) is at 0x12ff01
>
> - lpApplicationName is a null pointer
>
> - lpCommandLine is buggy. It points to this string :
> "..^Hinhyper.exe FILES\SN452\BIN\SNSDK.exe" toto"
> with ^H being the backspace char.
>
> Explanations are that my snsdk.exe is in
> d:\Program Files\SN452\bin, and that I gave it toto
> as a first argument (script to execute)
>

Thanks Xavier, it was very helpfull. I downloaded SN source code, and
tried to find what's wrong. Look at this :

- file : \SN452-source\snavigator\snavigator\win\makefile.am
        ....
        snsdk_SOURCES = winCon.c
        ....
        snsdk_CFLAGS =  -DAPPNAME=\"..\\bin\\hyper.exe\"
        ....

- file : \SN452-source\snavigator\snavigator\win\winCon.c

     /* create command string */
    strcpy(cmd, APPNAME);
    if (strchr(GetCommandLine(), ' '))
        strcat(cmd, strchr(GetCommandLine(), ' '));

    /* Create the child process. */
    if ( !CreateProcess (NULL,
                         cmd,           /* command
line                        */
                         NULL,          /* process security
attributes         */
                         NULL,          /* primary thread security
attributes  */
                         TRUE,          /* handles are
inherited               */
                         0,             /* creation
flags                      */
                         NULL,          /* use parent's
environment            */
                         NULL,          /* use parent's current
directory      */
                         &siStartInfo,  /* STARTUPINFO
pointer                 */
                         &piProcInfo))  /* receives
PROCESS_INFORMATION        */
        ErrorExit("CreateProcess failed");

Look at "create command string" : if it finds space in the comand line,
it will append to APPNAME the rest of the command line string (after the
space). That explains what you found :

"..^Hinhyper.exe FILES\SN452\BIN\SNSDK.exe" toto"

(APPNAME should be "..\bin\hyper.exe" but it seems to me that it sees it
as "^Hinhyper.exe" ;
 cmd is exactly what goes after space in "Program Files ..." :
"FILES\SN452\BIN\SNSDK.exe toto")

Am I wrong or cmd should be something like : "hyper.exe <script name>"
(in this case "hyper.exe toto") ?

See : http://msdn.microsoft.com/library/psdk/winbase/prothred_9dpv.htm
for CreateProcess
and : http://msdn.microsoft.com/library/psdk/winbase/prothred_0mzp.htm
for GetCommandLine (see there remark on CommandLineToArgvW).


Maybe I'm completely wrong ... If not, does someone has an idea of how
to make this thing work without having to change makefile or winCon.c
and recompile it on WinNT (I prefer ready-made binaries, to tell you the
truth) ?

Thanks.

Kind regards,
Marta.

Re: SNsdk on WinNT ?

[Marta Stojanovic]

Ian Roxborough wrote:

> Niels Skou Olsen wrote:
> > > - lpCommandLine is buggy. It points to this string :
> > > "..^Hinhyper.exe FILES\SN452\BIN\SNSDK.exe" toto"
>
> You could try installing it in a directory without a space.
> (I'm assuming you've installing it in something like
>  C:\Program Files\SN452......)
>
> The problem parsing the command line could be due to
> a space in the path name.
>
> I do remember SNsdk being funky in regards to which
> directory the scripts are in (I think they need to be
> in the same directory as SNsdk or something like that).

I tried both : I re-installed SN in D:\cygnus\sn452 (comparing to
previous D:\Program Files\cygnus\SN452) but I got the same error
message. Then I moved all the necessary files (my script + its input
files) in D:\cygnus\sn452\bin (or its parent directory), but it doesn't
work neither. I suppose that it has nothing to do with my script and its
position, because with or without it as an argument it gives the same
old CreateProcess error.

I'll try to find a way. But if the error is in SNsdk.exe (there I
couldn't help), do you have any other idea how to use SN database Tcl
API (hyper) on Win ?

Thank you all very much.

Kind regards,
Marta.

Re: SNsdk on WinNT ?

[Ian Roxborough]

Niels Skou Olsen wrote:
> > - lpCommandLine is buggy. It points to this string :
> > "..^Hinhyper.exe FILES\SN452\BIN\SNSDK.exe" toto"

You could try installing it in a directory without a space.
(I'm assuming you've installing it in something like
 C:\Program Files\SN452......)

The problem parsing the command line could be due to
a space in the path name.

I do remember SNsdk being funky in regards to which
directory the scripts are in (I think they need to be
in the same directory as SNsdk or something like that).

Ian.

Re: SNsdk on WinNT ?

[Niels Skou Olsen]

xavier.nodet@free.fr writes:

> From: sourcenav-owner@sources.redhat.com

> - lpApplicationName is a null pointer
> 
> - lpCommandLine is buggy. It points to this string :
> "..^Hinhyper.exe FILES\SN452\BIN\SNSDK.exe" toto"
> with ^H being the backspace char.

I agree that this is wrong. As I understand it, the only thing SNsdk.exe
does is re-map stdin/stdout and then start hyper.exe with the script
argument. So it seems that somehow SNsdk.exe messed up when "parsing"
argv[]. This should be fairly easy to track down..

Unfortunately I have neither sources nor build environment for SN/Windows
readily installed. Otherwise I would happily dig into it ;-)

> Explanations are that my snsdk.exe is in
> d:\Program Files\SN452\bin, and that I gave it toto
> as a first argument (script to execute)

Best regards,
-- 
Niels Skou Olsen, M.Sc.
Intelligent Engine, R&D
MAN B&W Diesel A/S

RE: SNsdk on WinNT ?

[Xavier Nodet]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

From: sourcenav-owner@sources.redhat.com
> [ mailto:sourcenav-owner@sources.redhat.com]On Behalf Of
> Niels Skou Olsen
> Sent: jeudi 14 décembre 2000 08:11
> To: sourcenav@sources.redhat.com
> Subject: Re: SNsdk on WinNT ?
>
> marta.stojanovic@nrc.ca writes:
>
>
> I wonder which file it cannot find. If only the error
> message had printed
> the first two arguments to CreateProcess(), the problem
> would be easier to
> narrow down.

Here is the definition of this function.

CreateProcessA(
    LPCSTR lpApplicationName,
    LPSTR lpCommandLine,
    LPSECURITY_ATTRIBUTES lpProcessAttributes,
    LPSECURITY_ATTRIBUTES lpThreadAttributes,
    BOOL bInheritHandles,
    DWORD dwCreationFlags,
    LPVOID lpEnvironment,
    LPCSTR lpCurrentDirectory,
    LPSTARTUPINFOA lpStartupInfo,
    LPPROCESS_INFORMATION lpProcessInformation
    );

I traced snsdk.exe and found the following arguments for
the first call to this function (it crashes in this function) :

- the return address (next instruction to execute
after returning from the function) is at 0x12ff01

- lpApplicationName is a null pointer

- lpCommandLine is buggy. It points to this string :
"..^Hinhyper.exe FILES\SN452\BIN\SNSDK.exe" toto"
with ^H being the backspace char.

Explanations are that my snsdk.exe is in
d:\Program Files\SN452\bin, and that I gave it toto
as a first argument (script to execute)

- The next two arguments (lpProcessAttributes and
lpThreadAttributes) are null pointers, bInheritHandles
is true, dwCreationFlags is 0, lpEnvironment is null,
lpCurrentDirectory is null,

- lpStartupInfo and lpProcessInformation seem
to have reasonable values (that is, they point to
a location that seems be in the program's memory).

Unfortunately, I have not enough knowledge of the
Windows API, nor time, to do much more...

Hope this will help,

--
Xavier Nodet

Re: SNsdk on WinNT ?

[Niels Skou Olsen]

marta.stojanovic@nrc.ca writes:

> now : I'm not able to run a Tcl script using SNsdk on WinNt. The error
> message is :
> 
>     Error in startup: CreateProcess failed: The system cannot find the
> file   specified.
> 
> This message appears when trying to run SNsdk from MSDOS prompt, both
> alone and with my Tcl file as an argument.

I have the same problems that Marta describe. This is on NT4.0 SP6a with
SN-4.5.2.

I wonder which file it cannot find. If only the error message had printed
the first two arguments to CreateProcess(), the problem would be easier to
narrow down.

Best regards,
-- 
Niels Skou Olsen, M.Sc.
Intelligent Engine, R&D
MAN B&W Diesel A/S

Re: SNsdk on WinNT ?

[Mo DeJong]

On Wed, 13 Dec 2000, Marta Stojanovic wrote:

> Hi all!
> 
> I saw a (unfortunatelly unanswered)  message from Andrew Brackley on SN
> mailing list (dated July 27 2000). He had the exact same problem as I do
> 
> now : I'm not able to run a Tcl script using SNsdk on WinNt. The error
> message is :
> 
>     Error in startup: CreateProcess failed: The system cannot find the
> file   specified.
> 
> This message appears when trying to run SNsdk from MSDOS prompt, both
> alone and with my Tcl file as an argument.
> 
> I assumed that it has something to do with environment, so I set
> TCL_LIBRARY as I did on Linux, I also put SN452/bin and
> SN452/share/Tcl8.1 in PATH, but it doesn't work.
> 
> I tried to run it from the console opened by hyper, but it doesn't work
> either.
> 
> I would really like to avoid using Cygwin - as Andrew proposed -(to make
> 
> it easier to use. From the SN doc it seems that it should work without
> it.


CreateProcess is an NT thing. It is like a fork+exec, it must
mean that the system can not find a program it wants to run.
This has nothing to do with TCL_LIBRARY or anything like
that. You are going to have to debug this one yourself,
I would say double check that the fully qualified SN bin dir
is on your PATH. You should just be able to run SN by double
clicking on the SN program from the Windows Explorer.

Good luck.

Mo DeJong
Red Hat Inc

SNsdk on WinNT ?

[Marta Stojanovic]

Hi all!

I saw a (unfortunatelly unanswered)  message from Andrew Brackley on SN
mailing list (dated July 27 2000). He had the exact same problem as I do

now : I'm not able to run a Tcl script using SNsdk on WinNt. The error
message is :

    Error in startup: CreateProcess failed: The system cannot find the
file   specified.

This message appears when trying to run SNsdk from MSDOS prompt, both
alone and with my Tcl file as an argument.

I assumed that it has something to do with environment, so I set
TCL_LIBRARY as I did on Linux, I also put SN452/bin and
SN452/share/Tcl8.1 in PATH, but it doesn't work.

I tried to run it from the console opened by hyper, but it doesn't work
either.

I would really like to avoid using Cygwin - as Andrew proposed -(to make

it easier to use. From the SN doc it seems that it should work without
it.

Do you have any idea ?

Thanks a lot in advance.

Kind regards,
Marta.

P.S. My script works fine on Linux (I set TCL_LIBRARY and left the first

three lines used to start wish : "exec hyper ..."). For NT I left out
these lines.