This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: patch to ignore SIGPWR and SIGXCPU (used by pthreads)


Andrew Cagney wrote:
> 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.

How does a program exceed its CPU usage?  In any other situation except
by having a person running the program explicitly set the CPU usage?
Somebody who knows how to to do that can be expected to know how to
use the 'handle' command.  On the other hand, we should not expect
someone debugging a Java program to have to use 'handle'.  That is
not acceptable, so we need to figure some way to fix this problem.

Is there a way that gdb can check if the inferior has set a non-default
signal handler, and only stop if using the default handler (or of
course if 'handle' was explicitly set)?
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/per/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]