public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "evans_chen1 at dell dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27244] New: GDB doesn't catch SIGCHLD Date: Mon, 25 Jan 2021 21:13:18 +0000 [thread overview] Message-ID: <bug-27244-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27244 Bug ID: 27244 Summary: GDB doesn't catch SIGCHLD Product: gdb Version: 10.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: evans_chen1 at dell dot com Target Milestone: --- Created attachment 13154 --> https://sourceware.org/bugzilla/attachment.cgi?id=13154&action=edit sig.c GDB Version: GNU gdb (GDB) 10.1 [GDB v10.1 for FreeBSD] Machine: Virtualbox FreeBSD 12.2 RELEASE amd64 VHD virtual machine Compiler used to compile GDB: FreeBSD clang version 8.0.1 Compiler used to compile the program: FreeBSD clang version 10.0.1, target x86_64-unknown-freebsd12.2 Command used to compile: clang -ggdb sig.c -o sig Source file “sig.c” is attached. Description of incorrect behavior: The following output was produced. For some reason, the SIGCHLD catchpoint didn't activate and "Program received SIGCHLD" was not printed. ---BEGIN OUTPUT--- (gdb) catch signal SIGCHLD Catchpoint 1 (signal SIGCHLD) (gdb) r Starting program: /root/sig Finished. [Inferior 1 (process 12929) exited normally] (gdb) handle SIGCHLD print Signal Stop Print Pass to program Description SIGCHLD No Yes Yes Child status changed (gdb) r Starting program: /root/sig Finished. [Inferior 1 (process 12983) exited normally] ---END OUTPUT--- -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-01-25 21:13 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 21:13 evans_chen1 at dell dot com [this message] 2023-01-04 1:50 ` [Bug tdep/27244] " tromey at sourceware dot 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-27244-4717@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).