1 ------------------------------------------------------------------------------
3 -- GNAT COMPILER COMPONENTS --
5 -- S Y S T E M . O S _ L I B --
9 -- Copyright (C) 1995-2016, Free Software Foundation, Inc. --
11 -- GNAT is free software; you can redistribute it and/or modify it under --
12 -- terms of the GNU General Public License as published by the Free Soft- --
13 -- ware Foundation; either version 3, or (at your option) any later ver- --
14 -- sion. GNAT is distributed in the hope that it will be useful, but WITH- --
15 -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --
16 -- or FITNESS FOR A PARTICULAR PURPOSE. --
18 -- As a special exception under Section 7 of GPL version 3, you are granted --
19 -- additional permissions described in the GCC Runtime Library Exception, --
20 -- version 3.1, as published by the Free Software Foundation. --
22 -- You should have received a copy of the GNU General Public License and --
23 -- a copy of the GCC Runtime Library Exception along with this program; --
24 -- see the files COPYING3 and COPYING.RUNTIME respectively. If not, see --
25 -- <http://www.gnu.org/licenses/>. --
27 -- GNAT was originally developed by the GNAT team at New York University. --
28 -- Extensive contributions were provided by Ada Core Technologies Inc. --
30 ------------------------------------------------------------------------------
32 -- Operating system interface facilities
34 -- This package contains types and procedures for interfacing to the
35 -- underlying OS. It is used by the GNAT compiler and by tools associated
36 -- with the GNAT compiler, and therefore works for the various operating
37 -- systems to which GNAT has been ported. This package will undoubtedly grow
38 -- as new services are needed by various tools.
40 -- This package tends to use fairly low-level Ada in order to not bring in
41 -- large portions of the RTL. For example, functions return access to string
42 -- as part of avoiding functions returning unconstrained types.
44 -- Except where specifically noted, these routines are portable across all
45 -- GNAT implementations on all supported operating systems.
47 -- Note: this package is in the System hierarchy so that it can be directly
48 -- be used by other predefined packages. User access to this package is via
49 -- a renaming of this package in GNAT.OS_Lib (file g-os_lib.ads).
51 pragma Compiler_Unit_Warning
;
56 package System
.OS_Lib
is
59 -----------------------
60 -- String Operations --
61 -----------------------
63 -- These are reexported from package Strings (which was introduced to
64 -- avoid different packages declaring different types unnecessarily).
65 -- See package System.Strings for details.
67 subtype String_Access
is Strings
.String_Access
;
69 function "=" (Left
: String_Access
; Right
: String_Access
) return Boolean
72 procedure Free
(X
: in out String_Access
) renames Strings
.Free
;
74 subtype String_List
is Strings
.String_List
;
76 function "=" (Left
: String_List
; Right
: String_List
) return Boolean
79 function "&" (Left
: String_Access
; Right
: String_Access
)
80 return String_List
renames Strings
."&";
81 function "&" (Left
: String_Access
; Right
: String_List
)
82 return String_List
renames Strings
."&";
83 function "&" (Left
: String_List
; Right
: String_Access
)
84 return String_List
renames Strings
."&";
85 function "&" (Left
: String_List
; Right
: String_List
)
86 return String_List
renames Strings
."&";
88 subtype String_List_Access
is Strings
.String_List_Access
;
91 (Left
: String_List_Access
;
92 Right
: String_List_Access
) return Boolean renames Strings
."=";
94 procedure Free
(Arg
: in out String_List_Access
) renames Strings
.Free
;
100 type OS_Time
is private;
101 -- The OS's notion of time is represented by the private type OS_Time. This
102 -- is the type returned by the File_Time_Stamp functions to obtain the time
103 -- stamp of a specified file. Functions and a procedure (modeled after the
104 -- similar subprograms in package Calendar) are provided for extracting
105 -- information from a value of this type. Although these are called GM, the
106 -- intention in the case of time stamps is not that they provide GMT times
107 -- in all cases but rather the actual (time-zone independent) time stamp of
108 -- the file (of course in Unix systems, this *is* in GMT form).
110 Invalid_Time
: constant OS_Time
;
111 -- A special unique value used to flag an invalid time stamp value
113 function "<" (X
: OS_Time
; Y
: OS_Time
) return Boolean;
114 function ">" (X
: OS_Time
; Y
: OS_Time
) return Boolean;
115 function ">=" (X
: OS_Time
; Y
: OS_Time
) return Boolean;
116 function "<=" (X
: OS_Time
; Y
: OS_Time
) return Boolean;
117 -- Basic comparison operators on OS_Time with obvious meanings. Note that
118 -- these have Intrinsic convention, so for example it is not permissible
119 -- to create accesses to any of these functions.
121 subtype Year_Type
is Integer range 1900 .. 2099;
122 subtype Month_Type
is Integer range 1 .. 12;
123 subtype Day_Type
is Integer range 1 .. 31;
124 subtype Hour_Type
is Integer range 0 .. 23;
125 subtype Minute_Type
is Integer range 0 .. 59;
126 subtype Second_Type
is Integer range 0 .. 59;
127 -- Declarations similar to those in Calendar, breaking down the time
129 function Current_Time
return OS_Time
;
130 -- Return the system clock value as OS_Time
132 function Current_Time_String
return String;
133 -- Returns current local time in the form YYYY-MM-DD HH:MM:SS. The result
134 -- has bounds 1 .. 19.
136 function GM_Year
(Date
: OS_Time
) return Year_Type
;
137 function GM_Month
(Date
: OS_Time
) return Month_Type
;
138 function GM_Day
(Date
: OS_Time
) return Day_Type
;
139 function GM_Hour
(Date
: OS_Time
) return Hour_Type
;
140 function GM_Minute
(Date
: OS_Time
) return Minute_Type
;
141 function GM_Second
(Date
: OS_Time
) return Second_Type
;
142 -- Functions to extract information from OS_Time value in GMT form
146 Year
: out Year_Type
;
147 Month
: out Month_Type
;
149 Hour
: out Hour_Type
;
150 Minute
: out Minute_Type
;
151 Second
: out Second_Type
);
152 -- Analogous to the Split routine in Ada.Calendar, takes an OS_Time and
153 -- provides a representation of it as a set of component parts, to be
154 -- interpreted as a date point in UTC.
161 Minute
: Minute_Type
;
162 Second
: Second_Type
) return OS_Time
;
163 -- Analogous to the Time_Of routine in Ada.Calendar, takes a set of time
164 -- component parts to be interpreted in the local time zone, and returns
165 -- an OS_Time. Returns Invalid_Time if the creation fails.
171 -- These routines give access to the open/creat/close/read/write level of
172 -- I/O routines in the typical C library (these functions are not part of
173 -- the ANSI C standard, but are typically available in all systems). See
174 -- also package Interfaces.C_Streams for access to the stream level
177 -- Note on file names. If a file name is passed as type String in any of
178 -- the following specifications, then the name is a normal Ada string and
179 -- need not be NUL-terminated. However, a trailing NUL character is
180 -- permitted, and will be ignored (more accurately, the NUL and any
181 -- characters that follow it will be ignored).
183 type File_Descriptor
is new Integer;
184 -- Corresponds to the int file handle values used in the C routines
186 Standin
: constant File_Descriptor
:= 0;
187 Standout
: constant File_Descriptor
:= 1;
188 Standerr
: constant File_Descriptor
:= 2;
189 -- File descriptors for standard input output files
191 Invalid_FD
: constant File_Descriptor
:= -1;
192 -- File descriptor returned when error in opening/creating file
194 procedure Close
(FD
: File_Descriptor
; Status
: out Boolean);
195 -- Close file referenced by FD. Status is False if the underlying service
196 -- failed. Reasons for failure include: disk full, disk quotas exceeded
197 -- and invalid file descriptor (the file may have been closed twice).
199 procedure Close
(FD
: File_Descriptor
);
200 -- Close file referenced by FD. This form is used when the caller wants to
201 -- ignore any possible error (see above for error cases).
205 -- Copy the file. It is an error if the target file already exists. The
206 -- time stamps and other file attributes are preserved in the copy.
209 -- If the target file exists, the file is replaced otherwise the file
210 -- is just copied. The time stamps and other file attributes are
211 -- preserved in the copy.
214 -- If the target file exists, the contents of the source file is
215 -- appended at the end. Otherwise the source file is just copied. The
216 -- time stamps and other file attributes are preserved if the
217 -- destination file does not exist.
221 -- Copy time stamps from source file to target file. All other
222 -- attributes are set to normal default values for file creation.
225 -- All attributes are copied from the source file to the target file.
226 -- This includes the timestamps, and for example also includes
227 -- read/write/execute attributes in Unix systems.
230 -- No attributes are copied. All attributes including the time stamp
231 -- values are set to normal default values for file creation.
233 -- Note: The default is Time_Stamps, which corresponds to the normal
234 -- default on Windows style systems. Full corresponds to the typical
235 -- effect of "cp -p" on Unix systems, and None corresponds to the typical
236 -- effect of "cp" on Unix systems.
238 -- Note: Time_Stamps and Full are not supported on VxWorks 5
243 Success
: out Boolean;
244 Mode
: Copy_Mode
:= Copy
;
245 Preserve
: Attribute
:= Time_Stamps
);
246 -- Copy a file. Name must designate a single file (no wild cards allowed).
247 -- Pathname can be a filename or directory name. In the latter case Name
248 -- is copied into the directory preserving the same file name. Mode
249 -- defines the kind of copy, see above with the default being a normal
250 -- copy in which the target file must not already exist. Success is set to
251 -- True or False indicating if the copy is successful (depending on the
254 procedure Copy_File_Attributes
257 Success
: out Boolean;
258 Copy_Timestamp
: Boolean := True;
259 Copy_Permissions
: Boolean := True);
260 -- Copy some of the file attributes from one file to another. Both files
261 -- must exist, or Success is set to False.
263 procedure Copy_Time_Stamps
266 Success
: out Boolean);
267 -- Copy Source file time stamps (last modification and last access time
268 -- stamps) to Dest file. Source and Dest must be valid filenames,
269 -- furthermore Dest must be writable. Success will be set to True if the
270 -- operation was successful and False otherwise.
272 -- Note: this procedure is not supported on VxWorks 5. On this platform,
273 -- Success is always set to False.
275 type Mode
is (Binary
, Text
);
276 for Mode
'Size use Integer'Size;
277 for Mode
use (Binary
=> 0, Text
=> 1);
278 -- Used in all the Open and Create calls to specify if the file is to be
279 -- opened in binary mode or text mode. In systems like Unix, this has no
280 -- effect, but in systems capable of text mode translation, the use of
281 -- Text as the mode parameter causes the system to do CR/LF translation
282 -- and also to recognize the DOS end of file character on input. The use
283 -- of Text where appropriate allows programs to take a portable Unix view
284 -- of DOS-format files and process them appropriately.
288 Fmode
: Mode
) return File_Descriptor
;
289 -- Creates new file with given name for writing, returning file descriptor
290 -- for subsequent use in Write calls. If the file already exists, it is
291 -- overwritten. File descriptor returned is Invalid_FD if file cannot be
292 -- successfully created.
294 function Create_New_File
296 Fmode
: Mode
) return File_Descriptor
;
297 -- Create new file with given name for writing, returning file descriptor
298 -- for subsequent use in Write calls. This differs from Create_File in
299 -- that it fails if the file already exists. File descriptor returned is
300 -- Invalid_FD if the file exists or cannot be created.
302 function Create_Output_Text_File
(Name
: String) return File_Descriptor
;
303 -- Creates new text file with given name suitable to redirect standard
304 -- output, returning file descriptor. File descriptor returned is
305 -- Invalid_FD if file cannot be successfully created.
307 Temp_File_Len
: constant Integer := 12;
308 -- Length of name returned by Create_Temp_File call (GNAT-XXXXXX & NUL)
310 subtype Temp_File_Name
is String (1 .. Temp_File_Len
);
311 -- String subtype set by Create_Temp_File
313 procedure Create_Temp_File
314 (FD
: out File_Descriptor
;
315 Name
: out Temp_File_Name
);
316 -- Create and open for writing a temporary file in the current working
317 -- directory. The name of the file and the File Descriptor are returned.
318 -- The File Descriptor returned is Invalid_FD in the case of failure. No
319 -- mode parameter is provided. Since this is a temporary file, there is no
320 -- point in doing text translation on it.
322 -- On some operating systems, the maximum number of temp files that can be
323 -- created with this procedure may be limited. When the maximum is reached,
324 -- this procedure returns Invalid_FD. On some operating systems, there may
325 -- be a race condition between processes trying to create temp files at the
326 -- same time in the same directory using this procedure.
328 procedure Create_Temp_File
329 (FD
: out File_Descriptor
;
330 Name
: out String_Access
);
331 -- Create and open for writing a temporary file in the current working
332 -- directory. The name of the file and the File Descriptor are returned.
333 -- It is the responsibility of the caller to deallocate the access value
336 -- The file is opened in binary mode (no text translation).
338 -- This procedure will always succeed if the current working directory is
339 -- writable. If the current working directory is not writable, then
340 -- Invalid_FD is returned for the file descriptor and null for the Name.
341 -- There is no race condition problem between processes trying to create
342 -- temp files at the same time in the same directory.
344 procedure Create_Temp_Output_File
345 (FD
: out File_Descriptor
;
346 Name
: out String_Access
);
347 -- Create and open for writing a temporary file in the current working
348 -- directory suitable to redirect standard output. The name of the file and
349 -- the File Descriptor are returned. It is the responsibility of the caller
350 -- to deallocate the access value returned in Name.
352 -- The file is opened in text mode
354 -- This procedure will always succeed if the current working directory is
355 -- writable. If the current working directory is not writable, then
356 -- Invalid_FD is returned for the file descriptor and null for the Name.
357 -- There is no race condition problem between processes trying to create
358 -- temp files at the same time in the same directory.
360 procedure Delete_File
(Name
: String; Success
: out Boolean);
361 -- Deletes file. Success is set True or False indicating if the delete is
364 function File_Length
(FD
: File_Descriptor
) return Long_Integer;
365 pragma Import
(C
, File_Length
, "__gnat_file_length_long");
367 type Large_File_Size
is range -2**63 .. 2**63 - 1;
368 -- Maximum supported size for a file (8 exabytes = 8 million terabytes,
369 -- should be enough to accomodate all possible needs for quite a while).
371 function File_Length64
(FD
: File_Descriptor
) return Large_File_Size
;
372 pragma Import
(C
, File_Length64
, "__gnat_file_length");
373 -- Get length of file from file descriptor FD
375 function File_Time_Stamp
(Name
: String) return OS_Time
;
376 -- Given the name of a file or directory, Name, obtains and returns the
377 -- time stamp. This function can be used for an unopened file. Returns
378 -- Invalid_Time is Name doesn't correspond to an existing file.
380 function File_Time_Stamp
(FD
: File_Descriptor
) return OS_Time
;
381 -- Get time stamp of file from file descriptor FD Returns Invalid_Time is
382 -- FD doesn't correspond to an existing file.
384 function Get_Debuggable_Suffix
return String_Access
;
385 -- Return the debuggable suffix convention. Usually this is the same as
386 -- the convention for Get_Executable_Suffix. The result is allocated on
387 -- the heap and should be freed after use to avoid storage leaks.
389 function Get_Executable_Suffix
return String_Access
;
390 -- Return the executable suffix convention. The result is allocated on the
391 -- heap and should be freed after use to avoid storage leaks.
393 function Get_Object_Suffix
return String_Access
;
394 -- Return the object suffix convention. The result is allocated on the heap
395 -- and should be freed after use to avoid storage leaks.
397 function Get_Target_Debuggable_Suffix
return String_Access
;
398 -- Return the target debuggable suffix convention. Usually this is the same
399 -- as the convention for Get_Executable_Suffix. The result is allocated on
400 -- the heap and should be freed after use to avoid storage leaks.
402 function Get_Target_Executable_Suffix
return String_Access
;
403 -- Return the target executable suffix convention. The result is allocated
404 -- on the heap and should be freed after use to avoid storage leaks.
406 function Get_Target_Object_Suffix
return String_Access
;
407 -- Return the target object suffix convention. The result is allocated on
408 -- the heap and should be freed after use to avoid storage leaks.
410 function Is_Absolute_Path
(Name
: String) return Boolean;
411 -- Returns True if Name is an absolute path name, i.e. it designates a
412 -- file or directory absolutely rather than relative to another directory.
414 function Is_Directory
(Name
: String) return Boolean;
415 -- Determines if the given string, Name, is the name of a directory.
416 -- Returns True if so, False otherwise. Name may be an absolute path
417 -- name or a relative path name, including a simple file name. If it is
418 -- a relative path name, it is relative to the current working directory.
420 function Is_Executable_File
(Name
: String) return Boolean;
421 -- Determines if the given string, Name, is the name of an existing file
422 -- that is executable. Returns True if so, False otherwise. Note that this
423 -- function simply interrogates the file attributes (e.g. using the C
424 -- function stat), so it does not indicate a situation in which a file may
425 -- not actually be readable due to some other process having exclusive
428 function Is_Owner_Readable_File
(Name
: String) return Boolean;
429 -- Determines if the given string, Name, is the name of an existing file
430 -- that is readable. Returns True if so, False otherwise. Note that this
431 -- function simply interrogates the file attributes (e.g. using the C
432 -- function stat), so it does not indicate a situation in which a file may
433 -- not actually be readable due to some other process having exclusive
436 function Is_Regular_File
(Name
: String) return Boolean;
437 -- Determines if the given string, Name, is the name of an existing
438 -- regular file. Returns True if so, False otherwise. Name may be an
439 -- absolute path name or a relative path name, including a simple file
440 -- name. If it is a relative path name, it is relative to the current
441 -- working directory.
443 function Is_Symbolic_Link
(Name
: String) return Boolean;
444 -- Determines if the given string, Name, is the path of a symbolic link on
445 -- systems that support it. Returns True if so, False if the path is not a
446 -- symbolic link or if the system does not support symbolic links.
448 -- A symbolic link is an indirect pointer to a file; its directory entry
449 -- contains the name of the file to which it is linked. Symbolic links may
450 -- span file systems and may refer to directories.
452 function Is_Owner_Writable_File
(Name
: String) return Boolean;
453 -- Determines if the given string, Name, is the name of an existing file
454 -- that is writable. Returns True if so, False otherwise. Note that this
455 -- function simply interrogates the file attributes (e.g. using the C
456 -- function stat), so it does not indicate a situation in which a file may
457 -- not actually be writable due to some other process having exclusive
460 function Is_Read_Accessible_File
(Name
: String) return Boolean;
461 -- Determines if the given string, Name, is the name of an existing file
462 -- that is readable. Returns True if so, False otherwise.
464 function Is_Write_Accessible_File
(Name
: String) return Boolean;
465 -- Determines if the given string, Name, is the name of an existing file
466 -- that is writable. Returns True if so, False otherwise.
468 function Is_Readable_File
(Name
: String) return Boolean
469 renames Is_Read_Accessible_File
;
470 function Is_Writable_File
(Name
: String) return Boolean
471 renames Is_Write_Accessible_File
;
472 -- These subprograms provided for backward compatibility and should not be
473 -- used. Use Is_Owner_Readable_File/Is_Owner_Writable_File or
474 -- Is_Read_Accessible_File/Is_Write_Accessible_File instead.
476 function Locate_Exec_On_Path
(Exec_Name
: String) return String_Access
;
477 -- Try to locate an executable whose name is given by Exec_Name in the
478 -- directories listed in the environment Path. If the Exec_Name does not
479 -- have the executable suffix, it will be appended before the search.
480 -- Otherwise works like Locate_Regular_File below. If the executable is
481 -- not found, null is returned.
483 -- Note that this function allocates memory for the returned value. This
484 -- memory needs to be deallocated after use.
486 function Locate_Regular_File
488 Path
: String) return String_Access
;
489 -- Try to locate a regular file whose name is given by File_Name in the
490 -- directories listed in Path. If a file is found, its full pathname is
491 -- returned; otherwise, a null pointer is returned. If the File_Name given
492 -- is an absolute pathname, then Locate_Regular_File just checks that the
493 -- file exists and is a regular file. Otherwise, if the File_Name given
494 -- includes directory information, Locate_Regular_File first checks if the
495 -- file exists relative to the current directory. If it does not, or if
496 -- the File_Name given is a simple file name, the Path argument is parsed
497 -- according to OS conventions, and for each directory in the Path a check
498 -- is made if File_Name is a relative pathname of a regular file from that
501 -- Note that this function allocates some memory for the returned value.
502 -- This memory needs to be deallocated after use.
504 Seek_Cur
: constant := 1;
505 Seek_End
: constant := 2;
506 Seek_Set
: constant := 0;
507 -- Used to indicate origin for Lseek call
510 (FD
: File_Descriptor
;
511 offset
: Long_Integer;
513 pragma Import
(C
, Lseek
, "__gnat_lseek");
514 -- Sets the current file pointer to the indicated offset value, relative
515 -- to the current position (origin = SEEK_CUR), end of file (origin =
516 -- SEEK_END), or start of file (origin = SEEK_SET).
518 function Normalize_Pathname
520 Directory
: String := "";
521 Resolve_Links
: Boolean := True;
522 Case_Sensitive
: Boolean := True) return String;
523 -- Returns a file name as an absolute path name, resolving all relative
524 -- directories, and symbolic links. If Name is a relative path, it is
525 -- interpreted relative to Directory, or to the current directory if
526 -- Directory is the empty string (the default). The result returned is
527 -- the normalized name of the file, containing no "." or ".." components,
528 -- and no duplicated directory separators. For most cases, if two file
529 -- names designate the same file through different paths,
530 -- Normalize_Pathname will return the same canonical name in both cases.
531 -- However, there are cases when this is not true; for example, this is
532 -- not true in Unix for two hard links designating the same file.
534 -- On Windows, the returned path will start with a drive letter. If
535 -- Directory is empty (the default) and Name is a relative path or an
536 -- absolute path without drive letter, the letter of the current drive
537 -- will start the returned path. If Case_Sensitive is True (the default),
538 -- then this drive letter will be forced to upper case ("C:\...").
540 -- If Resolve_Links is set to True, then the symbolic links, on systems
541 -- that support them, will be fully converted to the name of the file or
542 -- directory pointed to. This is slightly less efficient, since it
543 -- requires system calls.
545 -- If Name cannot be resolved, is invalid (for example if it is too big) or
546 -- is null on entry (for example if there is symbolic link circularity,
547 -- e.g. A is a symbolic link for B, and B is a symbolic link for A), then
548 -- Normalize_Pathname returns an empty string.
550 -- For case-sensitive file systems, the value of Case_Sensitive parameter
551 -- is ignored. For file systems that are not case-sensitive, such as
552 -- Windows, if this parameter is set to False, then the file and directory
553 -- names are folded to lower case. This allows checking whether two files
554 -- are the same by applying this function to their names and comparing the
555 -- results. If Case_Sensitive is set to True, this function does not change
556 -- the casing of file and directory names.
560 Fmode
: Mode
) return File_Descriptor
;
561 -- Opens file Name for appending, returning its file descriptor. File
562 -- descriptor returned is Invalid_FD if the file cannot be successfully
567 Fmode
: Mode
) return File_Descriptor
;
568 -- Open file Name for reading, returning its file descriptor. File
569 -- descriptor returned is Invalid_FD if the file cannot be opened.
571 function Open_Read_Write
573 Fmode
: Mode
) return File_Descriptor
;
574 -- Open file Name for both reading and writing, returning its file
575 -- descriptor. File descriptor returned is Invalid_FD if the file
579 (FD
: File_Descriptor
;
581 N
: Integer) return Integer;
582 -- Read N bytes to address A from file referenced by FD. Returned value is
583 -- count of bytes actually read, which can be less than N at EOF.
585 procedure Rename_File
588 Success
: out Boolean);
589 -- Rename a file. Success is set True or False indicating if the rename is
590 -- successful or not.
592 -- WARNING: In one very important respect, this function is significantly
593 -- non-portable. If New_Name already exists then on Unix systems, the call
594 -- deletes the existing file, and the call signals success. On Windows, the
595 -- call fails, without doing the rename operation. See also the procedure
596 -- Ada.Directories.Rename, which portably provides the windows semantics,
597 -- i.e. fails if the output file already exists.
599 -- The following defines the mode for the Copy_File procedure below. Note
600 -- that "time stamps and other file attributes" in the descriptions below
601 -- refers to the creation and last modification times, and also the file
602 -- access (read/write/execute) status flags.
604 procedure Set_Close_On_Exec
605 (FD
: File_Descriptor
;
606 Close_On_Exec
: Boolean;
607 Status
: out Boolean);
608 -- When Close_On_Exec is True, mark FD to be closed automatically when new
609 -- program is executed by the calling process (i.e. prevent FD from being
610 -- inherited by child processes). When Close_On_Exec is False, mark FD to
611 -- not be closed on exec (i.e. allow it to be inherited). Status is False
612 -- if the operation could not be performed.
614 S_Owner
: constant := 1;
615 S_Group
: constant := 2;
616 S_Others
: constant := 4;
617 -- Constants for use in Mode parameter to Set_Executable
619 procedure Set_Executable
(Name
: String; Mode
: Positive := S_Owner
);
620 -- Change permissions on the file given by Name to make it executable
621 -- for its owner, group or others, according to the setting of Mode.
622 -- As indicated, the default if no Mode parameter is given is owner.
624 procedure Set_File_Last_Modify_Time_Stamp
(Name
: String; Time
: OS_Time
);
625 -- Given the name of a file or directory, Name, set the last modification
626 -- time stamp. This function must be used for an unopened file.
628 procedure Set_Non_Readable
(Name
: String);
629 -- Change permissions on the named file to make it non-readable for
630 -- its owner. The writable and executable permissions are not
633 procedure Set_Non_Writable
(Name
: String);
634 -- Change permissions on the named file to make it non-writable for its
635 -- owner. The readable and executable permissions are not modified.
637 procedure Set_Read_Only
(Name
: String) renames Set_Non_Writable
;
638 -- This renaming is provided for backwards compatibility with previous
639 -- versions. The use of Set_Non_Writable is preferred (clearer name).
641 procedure Set_Readable
(Name
: String);
642 -- Change permissions on the named file to make it readable for its
645 procedure Set_Writable
(Name
: String);
646 -- Change permissions on the named file to make it writable for its owner
649 (FD
: File_Descriptor
;
651 N
: Integer) return Integer;
652 -- Write N bytes from address A to file referenced by FD. The returned
653 -- value is the number of bytes written, which can be less than N if a
654 -- disk full condition was detected.
656 -- The following section contains low-level routines using addresses to
657 -- pass file name and executable name. In each routine the name must be
658 -- Nul-Terminated. For complete documentation refer to the equivalent
659 -- routine (using String in place of C_File_Name) defined above.
661 subtype C_File_Name
is System
.Address
;
662 -- This subtype is used to document that a parameter is the address of a
663 -- null-terminated string containing the name of a file.
665 -- All the following functions need comments ???
669 Pathname
: C_File_Name
;
670 Success
: out Boolean;
671 Mode
: Copy_Mode
:= Copy
;
672 Preserve
: Attribute
:= Time_Stamps
);
674 procedure Copy_Time_Stamps
675 (Source
: C_File_Name
;
677 Success
: out Boolean);
681 Fmode
: Mode
) return File_Descriptor
;
683 function Create_New_File
685 Fmode
: Mode
) return File_Descriptor
;
687 procedure Delete_File
(Name
: C_File_Name
; Success
: out Boolean);
689 function File_Time_Stamp
(Name
: C_File_Name
) return OS_Time
;
690 -- Returns Invalid_Time is Name doesn't correspond to an existing file
692 function Is_Directory
(Name
: C_File_Name
) return Boolean;
693 function Is_Executable_File
(Name
: C_File_Name
) return Boolean;
694 function Is_Owner_Readable_File
(Name
: C_File_Name
) return Boolean;
695 function Is_Regular_File
(Name
: C_File_Name
) return Boolean;
696 function Is_Symbolic_Link
(Name
: C_File_Name
) return Boolean;
697 function Is_Owner_Writable_File
(Name
: C_File_Name
) return Boolean;
699 function Locate_Regular_File
700 (File_Name
: C_File_Name
;
701 Path
: C_File_Name
) return String_Access
;
705 Fmode
: Mode
) return File_Descriptor
;
709 Fmode
: Mode
) return File_Descriptor
;
711 function Open_Read_Write
713 Fmode
: Mode
) return File_Descriptor
;
715 procedure Rename_File
716 (Old_Name
: C_File_Name
;
717 New_Name
: C_File_Name
;
718 Success
: out Boolean);
724 subtype Argument_List
is String_List
;
725 -- Type used for argument list in call to Spawn. The lower bound of the
726 -- array should be 1, and the length of the array indicates the number of
729 subtype Argument_List_Access
is String_List_Access
;
730 -- Type used to return Argument_List without dragging in secondary stack.
731 -- Note that there is a Free procedure declared for this subtype which
732 -- frees the array and all referenced strings.
734 type Process_Id
is private;
735 -- A private type used to identify a process activated by the following
736 -- non-blocking calls. The only meaningful operation on this type is a
737 -- comparison for equality.
739 Invalid_Pid
: constant Process_Id
;
740 -- A special value used to indicate errors, as described below
742 function Current_Process_Id
return Process_Id
;
743 -- Returns the current process id or Invalid_Pid if not supported by the
746 function Argument_String_To_List
747 (Arg_String
: String) return Argument_List_Access
;
748 -- Take a string that is a program and its arguments and parse it into an
749 -- Argument_List. Note that the result is allocated on the heap, and must
750 -- be freed by the programmer (when it is no longer needed) to avoid
752 -- On Windows, backslashes are used as directory separators. On Unix,
753 -- however, they are used to escape the following character, so that for
754 -- instance "-d=name\ with\ space" is a single argument. In the result
755 -- list, the backslashes have been cleaned up when needed. The previous
756 -- example will thus result a single-element array, where the element is
757 -- "-d=name with space" (Unix) or "-d=name\ with\ space" (windows).
759 procedure Kill
(Pid
: Process_Id
; Hard_Kill
: Boolean := True);
760 -- Kill the process designated by Pid. Does nothing if Pid is Invalid_Pid
761 -- or on platforms where it is not supported, such as VxWorks. Hard_Kill
762 -- is True by default, and when True the process is terminated immediately.
763 -- If Hard_Kill is False, then a signal SIGINT is sent to the process on
764 -- POSIX OS or a ctrl-C event on Windows, allowing the process a chance to
765 -- terminate properly using a corresponding handler.
767 procedure Kill_Process_Tree
(Pid
: Process_Id
; Hard_Kill
: Boolean := True);
768 -- Kill the process designated by Pid and all it's children processes.
769 -- Does nothing if Pid is Invalid_Pid or on platforms where it is not
770 -- supported, such as VxWorks. Hard_Kill is True by default, and when True
771 -- the processes are terminated immediately. If Hard_Kill is False, then a
772 -- signal SIGINT is sent to the processes on POSIX OS or a ctrl-C event
773 -- on Windows, allowing the processes a chance to terminate properly
774 -- using a corresponding handler.
776 -- Note that this routine is not atomic and is supported only on Linux
777 -- and Windows. On other OS it will only kill the process identified by
780 function Non_Blocking_Spawn
781 (Program_Name
: String;
782 Args
: Argument_List
) return Process_Id
;
783 -- This is a non blocking call. The Process_Id of the spawned process is
784 -- returned. Parameters are to be used as in Spawn. If Invalid_Pid is
785 -- returned the program could not be spawned.
787 -- Spawning processes from tasking programs is not recommended. See
788 -- "NOTE: Spawn in tasking programs" below.
790 -- This function will always return Invalid_Pid under VxWorks, since there
791 -- is no notion of executables under this OS.
793 function Non_Blocking_Spawn
794 (Program_Name
: String;
795 Args
: Argument_List
;
796 Output_File_Descriptor
: File_Descriptor
;
797 Err_To_Out
: Boolean := True) return Process_Id
;
798 -- Similar to the procedure above, but redirects the output to the file
799 -- designated by Output_File_Descriptor. If Err_To_Out is True, then the
800 -- Standard Error output is also redirected. Invalid_Pid is returned
801 -- if the program could not be spawned successfully.
803 -- Spawning processes from tasking programs is not recommended. See
804 -- "NOTE: Spawn in tasking programs" below.
806 -- This function will always return Invalid_Pid under VxWorks, since there
807 -- is no notion of executables under this OS.
809 function Non_Blocking_Spawn
810 (Program_Name
: String;
811 Args
: Argument_List
;
812 Output_File
: String;
813 Err_To_Out
: Boolean := True) return Process_Id
;
814 -- Similar to the procedure above, but saves the output of the command to
815 -- a file with the name Output_File.
817 -- Invalid_Pid is returned if the output file could not be created or if
818 -- the program could not be spawned successfully.
820 -- Spawning processes from tasking programs is not recommended. See
821 -- "NOTE: Spawn in tasking programs" below.
823 -- This function will always return Invalid_Pid under VxWorks, since there
824 -- is no notion of executables under this OS.
826 function Non_Blocking_Spawn
827 (Program_Name
: String;
828 Args
: Argument_List
;
829 Stdout_File
: String;
830 Stderr_File
: String) return Process_Id
;
831 -- Similar to the procedure above, but saves the standard output of the
832 -- command to a file with the name Stdout_File and the standard output
833 -- of the command to a file with the name Stderr_File.
835 procedure Normalize_Arguments
(Args
: in out Argument_List
);
836 -- Normalize all arguments in the list. This ensure that the argument list
837 -- is compatible with the running OS and will works fine with Spawn and
838 -- Non_Blocking_Spawn for example. If Normalize_Arguments is called twice
839 -- on the same list it will do nothing the second time. Note that Spawn
840 -- and Non_Blocking_Spawn call Normalize_Arguments automatically, but
841 -- since there is a guarantee that a second call does nothing, this
842 -- internal call will have no effect if Normalize_Arguments is called
843 -- before calling Spawn. The call to Normalize_Arguments assumes that the
844 -- individual referenced arguments in Argument_List are on the heap, and
845 -- may free them and reallocate if they are modified.
847 function Pid_To_Integer
(Pid
: Process_Id
) return Integer;
848 -- Convert a process id to an Integer. Useful for writing hash functions
849 -- for type Process_Id or to compare two Process_Id (e.g. for sorting).
852 (Program_Name
: String;
853 Args
: Argument_List
;
854 Success
: out Boolean);
855 -- This procedure spawns a program with a given list of arguments. The
856 -- first parameter of is the name of the executable. The second parameter
857 -- contains the arguments to be passed to this program. Success is False
858 -- if the named program could not be spawned or its execution completed
859 -- unsuccessfully. Note that the caller will be blocked until the
860 -- execution of the spawned program is complete. For maximum portability,
861 -- use a full path name for the Program_Name argument. On some systems
862 -- (notably Unix systems) a simple file name may also work (if the
863 -- executable can be located in the path).
865 -- Spawning processes from tasking programs is not recommended. See
866 -- "NOTE: Spawn in tasking programs" below.
868 -- Note: Arguments in Args that contain spaces and/or quotes such as
869 -- "--GCC=gcc -v" or "--GCC=""gcc -v""" are not portable across all
870 -- operating systems, and would not have the desired effect if they were
871 -- passed directly to the operating system. To avoid this problem, Spawn
872 -- makes an internal call to Normalize_Arguments, which ensures that such
873 -- arguments are modified in a manner that ensures that the desired effect
874 -- is obtained on all operating systems. The caller may call
875 -- Normalize_Arguments explicitly before the call (e.g. to print out the
876 -- exact form of arguments passed to the operating system). In this case
877 -- the guarantee a second call to Normalize_Arguments has no effect
878 -- ensures that the internal call will not affect the result. Note that
879 -- the implicit call to Normalize_Arguments may free and reallocate some
880 -- of the individual arguments.
882 -- This function will always set Success to False under VxWorks and other
883 -- similar operating systems which have no notion of the concept of
884 -- dynamically executable file. Otherwise Success is set True if the exit
885 -- status of the spawned process is zero.
888 (Program_Name
: String;
889 Args
: Argument_List
) return Integer;
890 -- Similar to the above procedure, but returns the actual status returned
891 -- by the operating system, or -1 under VxWorks and any other similar
892 -- operating systems which have no notion of separately spawnable programs.
894 -- Spawning processes from tasking programs is not recommended. See
895 -- "NOTE: Spawn in tasking programs" below.
898 (Program_Name
: String;
899 Args
: Argument_List
;
900 Output_File_Descriptor
: File_Descriptor
;
901 Return_Code
: out Integer;
902 Err_To_Out
: Boolean := True);
903 -- Similar to the procedure above, but redirects the output to the file
904 -- designated by Output_File_Descriptor. If Err_To_Out is True, then the
905 -- Standard Error output is also redirected.
906 -- Return_Code is set to the status code returned by the operating system
908 -- Spawning processes from tasking programs is not recommended. See
909 -- "NOTE: Spawn in tasking programs" below.
912 (Program_Name
: String;
913 Args
: Argument_List
;
914 Output_File
: String;
915 Success
: out Boolean;
916 Return_Code
: out Integer;
917 Err_To_Out
: Boolean := True);
918 -- Similar to the procedure above, but saves the output of the command to
919 -- a file with the name Output_File.
921 -- Success is set to True if the command is executed and its output
922 -- successfully written to the file. If Success is True, then Return_Code
923 -- will be set to the status code returned by the operating system.
924 -- Otherwise, Return_Code is undefined.
926 -- Spawning processes from tasking programs is not recommended. See
927 -- "NOTE: Spawn in tasking programs" below.
929 procedure Wait_Process
(Pid
: out Process_Id
; Success
: out Boolean);
930 -- Wait for the completion of any of the processes created by previous
931 -- calls to Non_Blocking_Spawn. The caller will be suspended until one of
932 -- these processes terminates (normally or abnormally). If any of these
933 -- subprocesses terminates prior to the call to Wait_Process (and has not
934 -- been returned by a previous call to Wait_Process), then the call to
935 -- Wait_Process is immediate. Pid identifies the process that has
936 -- terminated (matching the value returned from Non_Blocking_Spawn).
937 -- Success is set to True if this sub-process terminated successfully. If
938 -- Pid = Invalid_Pid, there were no subprocesses left to wait on.
940 -- This function will always set success to False under VxWorks, since
941 -- there is no notion of executables under this OS.
943 -------------------------------------
944 -- NOTE: Spawn in Tasking Programs --
945 -------------------------------------
947 -- Spawning processes in tasking programs using the above Spawn and
948 -- Non_Blocking_Spawn subprograms is not recommended, because there are
949 -- subtle interactions between creating a process and signals/locks that
950 -- can cause trouble. These issues are not specific to Ada; they depend
951 -- primarily on the operating system.
953 -- If you need to spawn processes in a tasking program, you will need to
954 -- understand the semantics of your operating system, and you are likely to
955 -- write non-portable code, because operating systems differ in this area.
957 -- The Spawn and Non_Blocking_Spawn subprograms call the following
958 -- operating system functions:
960 -- On Windows: spawnvp (blocking) or CreateProcess (non-blocking)
962 -- On Solaris: fork1, followed in the child process by execv
964 -- On other Unix-like systems: fork, followed in the child
967 -- On vxworks, spawning of processes is not supported
969 -- For details, look at the functions __gnat_portable_spawn and
970 -- __gnat_portable_no_block_spawn in adaint.c.
972 -- You should read the operating-system-specific documentation for the
973 -- above functions, paying special attention to subtle interactions with
974 -- threading, signals, locks, and file descriptors. Most of the issues are
975 -- related to the fact that on Unix, there is a window of time between fork
976 -- and execv; Windows does not have this problem, because spawning is done
977 -- in a single operation.
979 -- On Posix-compliant systems, such as Linux, fork duplicates just the
980 -- calling thread. (On Solaris, fork1 is the Posix-compliant version of
983 -- You should avoid using signals while spawning. This includes signals
984 -- used internally by the Ada run-time system, such as timer signals used
985 -- to implement delay statements.
987 -- It is best to spawn any subprocesses very early, before the parent
988 -- process creates tasks, locks, or installs signal handlers. Certainly
989 -- avoid doing simultaneous spawns from multiple threads of the same
992 -- There is no problem spawning a subprocess that uses tasking: the
993 -- problems are caused only by tasking in the parent.
995 -- If the parent is using tasking, and needs to spawn subprocesses at
996 -- arbitrary times, one technique is for the parent to spawn (very early)
997 -- a particular spawn-manager subprocess whose job is to spawn other
998 -- processes. The spawn-manager must avoid tasking. The parent sends
999 -- messages to the spawn-manager requesting it to spawn processes, using
1000 -- whatever inter-process communication mechanism you like, such as
1003 -- In short, mixing spawning of subprocesses with tasking is a tricky
1004 -- business, and should be avoided if possible, but if it is necessary,
1005 -- the above guidelines should be followed, and you should beware of
1006 -- portability problems.
1012 function Errno
return Integer;
1013 pragma Import
(C
, Errno
, "__get_errno");
1014 -- Return the task-safe last error number
1016 function Errno_Message
1017 (Err
: Integer := Errno
;
1018 Default
: String := "") return String;
1019 -- Return a message describing the given Errno value. If none is provided
1020 -- by the system, return Default if not empty, else return a generic
1021 -- message indicating the numeric errno value.
1023 function Getenv
(Name
: String) return String_Access
;
1024 -- Get the value of the environment variable. Returns an access to the
1025 -- empty string if the environment variable does not exist or has an
1026 -- explicit null value (in some operating systems these are distinct
1027 -- cases, in others they are not; this interface abstracts away that
1028 -- difference. The argument is allocated on the heap (even in the null
1029 -- case), and needs to be freed explicitly when no longer needed to avoid
1033 pragma Import
(C
, OS_Abort
, "abort");
1034 pragma No_Return
(OS_Abort
);
1035 -- Exit to OS signalling an abort (traceback or other appropriate
1036 -- diagnostic information should be given if possible, or entry made to
1037 -- the debugger if that is possible).
1039 procedure OS_Exit
(Status
: Integer);
1040 pragma No_Return
(OS_Exit
);
1041 -- Exit to OS with given status code (program is terminated). Note that
1042 -- this is abrupt termination. All tasks are immediately terminated. There
1043 -- are no finalization or other Ada-specific cleanup actions performed. On
1044 -- systems with atexit handlers (such as Unix and Windows), atexit handlers
1047 type OS_Exit_Subprogram
is access procedure (Status
: Integer);
1049 procedure OS_Exit_Default
(Status
: Integer);
1050 pragma No_Return
(OS_Exit_Default
);
1051 -- Default implementation of procedure OS_Exit
1053 OS_Exit_Ptr
: OS_Exit_Subprogram
:= OS_Exit_Default
'Access;
1054 -- OS_Exit is implemented through this access value. It it then possible to
1055 -- change the implementation of OS_Exit by redirecting OS_Exit_Ptr to an
1056 -- other implementation.
1058 procedure Set_Errno
(Errno
: Integer);
1059 pragma Import
(C
, Set_Errno
, "__set_errno");
1060 -- Set the task-safe error number
1062 procedure Setenv
(Name
: String; Value
: String);
1063 -- Set the value of the environment variable Name to Value. This call
1064 -- modifies the current environment, but does not modify the parent
1065 -- process environment. After a call to Setenv, Getenv (Name) will always
1066 -- return a String_Access referencing the same String as Value. This is
1067 -- true also for the null string case (the actual effect may be to either
1068 -- set an explicit null as the value, or to remove the entry, this is
1069 -- operating system dependent). Note that any following calls to Spawn
1070 -- will pass an environment to the spawned process that includes the
1071 -- changes made by Setenv calls.
1073 Directory_Separator
: constant Character;
1074 -- The character that is used to separate parts of a pathname
1076 Path_Separator
: constant Character;
1077 -- The character to separate paths in an environment variable value
1080 pragma Import
(C
, Path_Separator
, "__gnat_path_separator");
1081 pragma Import
(C
, Directory_Separator
, "__gnat_dir_separator");
1082 pragma Import
(C
, Current_Time
, "__gnat_current_time");
1083 pragma Import
(C
, Current_Process_Id
, "__gnat_current_process_id");
1086 range -(2 ** (Standard
'Address_Size - Integer'(1))) ..
1087 +(2 ** (Standard'Address_Size - Integer'(1)) - 1);
1088 -- Type used for timestamps in the compiler. This type is used to hold
1089 -- time stamps, but may have a different representation than C's time_t.
1090 -- This type needs to match the declaration of OS_Time in adaint.h.
1092 -- Add pragma Inline statements for comparison operations on OS_Time. It
1093 -- would actually be nice to use pragma Import (Intrinsic) here, but this
1094 -- was not properly supported till GNAT 3.15a, so that would cause
1095 -- bootstrap path problems. To be changed later ???
1097 Invalid_Time
: constant OS_Time
:= -1;
1098 -- This value should match the return value from __gnat_file_time_*
1100 pragma Inline
("<");
1101 pragma Inline
(">");
1102 pragma Inline
("<=");
1103 pragma Inline
(">=");
1105 type Process_Id
is new Integer;
1106 Invalid_Pid
: constant Process_Id
:= -1;