public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31203] [gdb] FAIL: gdb.base/kill-during-detach.exp: exit_p=true: checkpoint_p=true: python kill_and_detach() Date: Wed, 03 Jan 2024 10:58:58 +0000 [thread overview] Message-ID: <bug-31203-4717-ZnVkCfGtNN@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31203-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31203 --- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> --- I've investigated why this doesn't trigger on x86_64. I found that in the x86_64 case, we've only got fds 0, 1 and 2, and none of them get their file pointer restored, so inferior lseek is not called during linux_fork_detach. In contrast, in the m1 case, we've got fds 42 and 52, whose file pointers are to be restored to 0, so inferior lseek is called during linux_fork_detach. File descriptors in more detail: ... $ ls -la /proc/3487043/fd total 0 dr-x------. 2 vries vries 5 3 jan 11:41 . dr-xr-xr-x. 9 vries vries 0 3 jan 11:41 .. lrwx------. 1 vries vries 64 3 jan 11:41 0 -> /dev/pts/1 lrwx------. 1 vries vries 64 3 jan 11:41 1 -> /dev/pts/1 lrwx------. 1 vries vries 64 3 jan 11:41 2 -> /dev/pts/1 lr-x------. 1 vries vries 64 3 jan 11:41 42 -> anon_inode:inotify lrwx------. 1 vries vries 64 3 jan 11:41 52 -> '/memfd:pulseaudio (deleted)' ... So, my guess is that opening a file before the checkpoint and reading something from the file after the checkpoint will also trigger this on x86_64. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-03 10:59 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-01 20:04 [Bug gdb/31203] New: " vries at gcc dot gnu.org 2024-01-01 20:04 ` [Bug gdb/31203] " vries at gcc dot gnu.org 2024-01-02 8:01 ` vries at gcc dot gnu.org 2024-01-02 8:36 ` vries at gcc dot gnu.org 2024-01-03 8:47 ` vries at gcc dot gnu.org 2024-01-03 10:31 ` vries at gcc dot gnu.org 2024-01-03 10:58 ` vries at gcc dot gnu.org [this message] 2024-01-04 4:37 ` kevinb at redhat dot com 2024-01-04 11:20 ` vries at gcc dot gnu.org 2024-01-04 11:21 ` vries at gcc dot gnu.org 2024-01-08 16:29 ` vries at gcc dot gnu.org 2024-01-08 19:05 ` kevinb at redhat dot com 2024-01-09 16:57 ` vries at gcc dot gnu.org 2024-01-11 9:12 ` cvs-commit at gcc dot gnu.org 2024-01-11 9:13 ` vries at gcc dot gnu.org 2024-01-11 9:15 ` vries 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-31203-4717-ZnVkCfGtNN@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).