From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Per Bothner <per@bothner.com>, gdb-patches@sources.redhat.com
Subject: Re: patch to ignore SIGPWR and SIGXCPU (used by pthreads)
Date: Mon, 21 Jan 2002 09:32:00 -0000 [thread overview]
Message-ID: <3C4C4F81.7269@redhat.com> (raw)
In-Reply-To: <3C4BBF78.8050405@cygnus.com>
Andrew Cagney wrote:
>
> > Why not? What does it hurt to (by default) just pass them to the
> > inferior? Having gdb stop inconveniences (and confuses) everybody who
> > uses gcj. Having gdb silently pass the signals to the application
> > inconveniences/confuses - who?
>
> Consider SIGXCPU.
>
> With your proposed change, a program that exceeds its CPU usage will
> quietly terminate. The user will loose their entire debug session.
> This is very different to GDB's current behavour where the signal is
> intercepted, the program is stopped, and control is returned to the user.
Java's use of these signals is somewhat analogous to what
linux threads does. In that case, we also "silence" the
signals, but we do it only in the context where we know
they are used. Only for linux, and only when a multi-thread
program is detected.
Could you do something like that?
next prev parent reply other threads:[~2002-01-21 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 12:33 Per Bothner
2002-01-20 16:48 ` Andrew Cagney
2002-01-20 21:51 ` Per Bothner
2002-01-20 23:12 ` Andrew Cagney
2002-01-20 23:32 ` Per Bothner
2002-01-21 0:44 ` Andrew Cagney
2002-01-21 9:32 ` Michael Snyder [this message]
2002-01-21 10:39 ` Daniel Jacobowitz
2002-01-20 23:39 ` Per Bothner
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=3C4C4F81.7269@redhat.com \
--to=msnyder@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=per@bothner.com \
/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