From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,bc90e355ba0a1f8f X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-11-10 10:01:51 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!cyclone.bc.net!news.uunet.ca!nf3.bellglobal.com!nf1.bellglobal.com!nf2.bellglobal.com!news20.bellglobal.com.POSTED!not-for-mail From: "Warren W. Gay VE3WWG" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada multi-threaded programs do not terminate under RedHat Linux References: <43f0a81.0311071228.6620c6c2@posting.google.com> <_eYqb.1684$6c3.3@newsread1.news.pas.earthlink.net> In-Reply-To: <_eYqb.1684$6c3.3@newsread1.news.pas.earthlink.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4aQrb.953$IK2.97672@news20.bellglobal.com> Date: Mon, 10 Nov 2003 12:47:16 -0500 NNTP-Posting-Host: 198.96.223.163 X-Complaints-To: abuse@sympatico.ca X-Trace: news20.bellglobal.com 1068486400 198.96.223.163 (Mon, 10 Nov 2003 12:46:40 EST) NNTP-Posting-Date: Mon, 10 Nov 2003 12:46:40 EST Organization: Bell Sympatico Xref: archiver1.google.com comp.lang.ada:2312 Date: 2003-11-10T12:47:16-05:00 List-Id: Jeffrey Carter wrote: > Ruben Stranders wrote: > >> I've compiled it under RedHat Linux 9.0 with "gnatmake test.adb". >> Unfortunately, the resulting program doesn't terminate. Instead of the >> expected output: >> >> Starting >> Finished >> Test >> >> it only prints the first two lines. The body of the procedure "test" >> is never called. I've tried this with several other programs and on >> different machines (all with RedHat 9.0). Can anyone give me a >> pointer? > > > Usually, under Unixes such as Linux, when people try to run a program > called "test" nothing happens, since they're running a Unix utility > rather than their program. But if you're getting some of the output from > your program, I guess that's not the problem. If in doubt, always do a ./test if the executable is in your current directory (this is a good general practice anyway, to avoid trojan horses). If the executable is in another directory, then you can also invoke by pathname, starting from '/'. Without qualifying the name of the executable, Jeffrey is right: you usually end up invoking the shell test command (builtin, or otherwise). -- Warren W. Gay VE3WWG http://home.cogeco.ca/~ve3wwg