public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18653] New: spawn changes SIGPIPE SIG_DFL to SIG_IGN
Date: Fri, 10 Jul 2015 11:57:00 -0000	[thread overview]
Message-ID: <bug-18653-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18653

            Bug ID: 18653
           Summary: spawn changes SIGPIPE SIG_DFL to SIG_IGN
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: jan.kratochvil at redhat dot com
  Target Milestone: ---

That is a program run under GDB "run" behaves differently than standalone.

standalone:                 SIG_DFL
GDB linux-nat:        FAIL: SIG_IGN
GDB gdbserver legacy: PASS: SIG_DFL
GDB gdbserver multi:  FAIL: SIG_IGN

-----------------------------------------
#define _GNU_SOURCE
#include <stdio.h>
#include <signal.h>
int main(void) {
  sighandler_t s=signal(SIGPIPE,SIG_DFL);
  if (s==SIG_DFL) puts("SIG_DFL");
  if (s==SIG_IGN) puts("SIG_IGN");
  return 0;
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2015-07-10 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 11:57 jan.kratochvil at redhat dot com [this message]
2024-01-04 13:22 ` [Bug gdb/18653] " ssbssa at sourceware dot org
2024-01-05  4:36 ` pinskia 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-18653-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: 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).