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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,956e1c708fea1c33 X-Google-Attributes: gid103376,public From: Thomas Handler Subject: Re: Looking for implementation idea Date: 1999/02/10 Message-ID: <36C15BBE.F32B0963@systems.at>#1/1 X-Deja-AN: 442765252 Content-Transfer-Encoding: 7bit References: <36BD749B.DA735DB7@umundum.vol.at> <36BDCA84.74643242@icon.fi> <36BECDCC.F01C8D98@systems.at> <36C0B347.77286688@icon.fi> Content-Type: text/plain; charset=us-ascii Organization: SYSTEMS AG Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-02-10T00:00:00+00:00 List-Id: Niklas, Niklas Holsti wrote: > > > That problem sounds serious enough to report as a bug, either to ACT > > > or FSU. > > It seems obvious to me, just imagine what will happen, when you abort a > > call that has requested dynamic memory? I guess this memory will be > > lost. > "man select" on my Linux system does not indicate that is allocates > dynamic memory. From your description of the problem, it seems that I also had a look into the kernel sources (though I have to admit that I'm far far far away from being someone that knows enough about the linux kernel to find this problem) but there was nothin obvious I saw. > is a serious problem, and should interest at least the Ada on Linux Team. I will resent my original message to the Ada on Linux Team mailing list... > Exactly. ATC abort of Linux calls should not leak memory. Now, I > don't know how hard this is to correct, but at the very least there > should be some warnings about it in the GNAT documentation (... I have > to admit I haven't read the most recent docs). I have had a look on several books I have about Ada (RM, ARM, John Barnes's Prgramming in Ada 95, Concurrency in Ada and the GNAT docs but I haven't found anything describing ATC with respect to OS calls or leaking... > FSU functions to find out how they block; sorry I can't provide > positive info. I have made the tests and it's correct, read() and write() operate non-blocking even with FSU lib, but select() seems to block. Ciao, Thomas Handler