public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/102992] fortran: redirecting standard out to a file does not work on macOS 12.0
Date: Mon, 01 Nov 2021 12:49:18 +0000 [thread overview]
Message-ID: <bug-102992-4-D4v5SR8XdO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102992-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102992
--- Comment #18 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Thomas Koenig from comment #13)
> Here is a complete strace of a "Hello, world" program on Linux, compiled
> with -static-libgfortran (to remove some of the shared library loading :-)
> and executed with
>
> $ strace ./a.out > hello.dat
>
> execve("./a.out", ["./a.out"], 0x7fff23679850 /* 52 vars */) = 0
> brk(NULL) = 0x55795af28000
>
> Is it possible to run an equivalent command on MacOS to see
> what is going on there?
Seems that dtruss is doing the same under macOS, here I get this output for the
Hello, world! program:
SYSCALL(args) = return
Hello, world!\n
access("/AppleInternal/XBS/.isChrooted\0", 0x0, 0x0) = -1 Err#2
bsdthread_register(0x7FF805E18020, 0x7FF805E1800C, 0x2000) =
1073742303 0
shm_open(0x7FF805CE6F5D, 0x0, 0x5CE57BA) = 3 0
fstat64(0x3, 0x7FF7BDDDE820, 0x0) = 0 0
mmap(0x0, 0x2000, 0x1, 0x40001, 0x3, 0x0) = 0x102231000 0
close(0x3) = 0 0
ioctl(0x2, 0x4004667A, 0x7FF7BDDDE8D4) = 0 0
mprotect(0x102238000, 0x1000, 0x0) = 0 0
mprotect(0x10223F000, 0x1000, 0x0) = 0 0
mprotect(0x102240000, 0x1000, 0x0) = 0 0
mprotect(0x102247000, 0x1000, 0x0) = 0 0
mprotect(0x102233000, 0x90, 0x1) = 0 0
mprotect(0x102233000, 0x90, 0x3) = 0 0
mprotect(0x102233000, 0x90, 0x1) = 0 0
mprotect(0x102248000, 0x1000, 0x1) = 0 0
mprotect(0x102249000, 0x90, 0x1) = 0 0
mprotect(0x102249000, 0x90, 0x3) = 0 0
mprotect(0x102249000, 0x90, 0x1) = 0 0
mprotect(0x102233000, 0x90, 0x3) = 0 0
mprotect(0x102233000, 0x90, 0x1) = 0 0
mprotect(0x102248000, 0x1000, 0x3) = 0 0
mprotect(0x102248000, 0x1000, 0x1) = 0 0
issetugid(0x0, 0x0, 0x0) = 0 0
getentropy(0x7FF7BDDDE6D0, 0x20, 0x0) = 0 0
getentropy(0x7FF7BDDDE730, 0x40, 0x0) = 0 0
getpid(0x0, 0x0, 0x0) = 61321 0
stat64("/AppleInternal\0", 0x7FF7BDDDEDF0, 0x0) = -1 Err#2
csops_audittoken(0xEF89, 0x7, 0x7FF7BDDDE920) = -1 Err#22
proc_info(0x2, 0xEF89, 0xD) = 64 0
csops_audittoken(0xEF89, 0x7, 0x7FF7BDDDEA10) = -1 Err#22
sysctlbyname(kern.osvariant_status, 0x15, 0x7FF7BDDDEE40, 0x7FF7BDDDEE38, 0x0)
= 0 0
csops(0xEF89, 0x0, 0x7FF7BDDDEE74) = 0 0
fstat64(0x0, 0x7FF7BDDDEBF0, 0x0) = 0 0
fstat64(0x1, 0x7FF7BDDDEBF0, 0x0) = 0 0
fstat64(0x2, 0x7FF7BDDDEBF0, 0x0) = 0 0
mprotect(0x10212F000, 0x100000, 0x1) = 0 0
sigaction(0x3, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0x4, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0x6, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0x8, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0xB, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0xA, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0xC, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0x5, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0x18, 0x7FF7BDDDFFA8, 0x7FF7BDDDFFD0) = 0 0
sigaction(0x19, 0x7FF7BDDDFFB8, 0x7FF7BDDDFFE0) = 0 0
write(0x1, " Hello, world!\\n\n\0", 0x11) = 17 0
next prev parent reply other threads:[~2021-11-01 12:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 22:34 [Bug fortran/102992] New: Piping in a file does no longer work on macOS Monterey juergen.reuter at desy dot de
2021-10-28 22:37 ` [Bug fortran/102992] " juergen.reuter at desy dot de
2021-10-28 23:11 ` [Bug libfortran/102992] " iains at gcc dot gnu.org
2021-10-28 23:22 ` pinskia at gcc dot gnu.org
2021-10-29 6:41 ` juergen.reuter at desy dot de
2021-10-29 10:04 ` juergen.reuter at desy dot de
2021-10-29 12:40 ` iains at gcc dot gnu.org
2021-10-29 12:51 ` iains at gcc dot gnu.org
2021-10-29 13:12 ` [Bug libfortran/102992] fortran: redirecting standard out to a file does not work on macOS 12.0 iains at gcc dot gnu.org
2021-10-29 14:05 ` juergen.reuter at desy dot de
2021-10-29 15:50 ` juergen.reuter at desy dot de
2021-10-31 0:52 ` townsend at astro dot wisc.edu
2021-11-01 9:09 ` juergen.reuter at desy dot de
2021-11-01 10:51 ` tkoenig at gcc dot gnu.org
2021-11-01 11:10 ` tkoenig at gcc dot gnu.org
2021-11-01 11:17 ` tkoenig at gcc dot gnu.org
2021-11-01 12:22 ` iains at gcc dot gnu.org
2021-11-01 12:25 ` iains at gcc dot gnu.org
2021-11-01 12:49 ` juergen.reuter at desy dot de [this message]
2021-11-01 17:37 ` tkoenig at gcc dot gnu.org
2021-11-01 17:41 ` tkoenig at gcc dot gnu.org
2021-11-01 17:44 ` juergen.reuter at desy dot de
2021-11-01 17:50 ` juergen.reuter at desy dot de
2021-11-01 18:08 ` iains at gcc dot gnu.org
2021-11-01 18:53 ` juergen.reuter at desy dot de
2021-11-01 19:00 ` iains at gcc dot gnu.org
2021-11-01 20:47 ` iains at gcc dot gnu.org
2021-11-02 10:39 ` dominiq at lps dot ens.fr
2021-11-12 12:06 ` fxcoudert at gcc dot gnu.org
2021-11-12 12:31 ` iains at gcc dot gnu.org
2021-11-12 12:40 ` fxcoudert at gcc dot gnu.org
2021-11-15 19:32 ` juergen.reuter at desy dot de
2021-11-15 19:43 ` fxcoudert at gcc dot gnu.org
2021-11-15 19:51 ` cvs-commit at gcc dot gnu.org
2021-11-15 19:55 ` iains at gcc dot gnu.org
2021-12-14 18:39 ` juergen.reuter at desy dot de
2021-12-15 13:06 ` iains at gcc dot gnu.org
2021-12-15 14:06 ` fxcoudert at gcc dot gnu.org
2022-04-14 5:26 ` cvs-commit at gcc dot gnu.org
2022-05-06 8:31 ` jakub at gcc dot gnu.org
2022-05-29 19:15 ` cvs-commit at gcc dot gnu.org
2022-05-29 19:27 ` iains at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-102992-4-D4v5SR8XdO@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).