This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Readline: Cleanup some warnings
- From: Pedro Alves <palves at redhat dot com>
- To: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>, Tom Tromey <tom at tromey dot com>, Joel Brobecker <brobecker at adacore dot com>
- Cc: Alan Hayward <Alan dot Hayward at arm dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, nd <nd at arm dot com>
- Date: Wed, 6 Feb 2019 19:56:35 +0000
- Subject: Re: [PATCH] Readline: Cleanup some warnings
- References: <20190130085716.75179-1-alan.hayward@arm.com> <20190131075907.GA313@adacore.com> <F71F4EDA-CBDF-4B05-B9C2-588D02471EB2@arm.com> <3463805B-A8BF-4C20-ACE3-C21AE3F7DB62@arm.com> <20190201080533.GA31043@adacore.com> <877eejvfoq.fsf@tromey.com> <1549047248.2630.7.camel@skynet.be>
On 02/01/2019 06:54 PM, Philippe Waroquiers wrote:
>
> Switching to this readline version causes the following checks to fail:
> FAIL: gdb.gdb/selftest.exp: send SIGINT signal to child process (timeout)
> FAIL: gdb.gdb/selftest.exp: thread 1 (timeout)
> FAIL: gdb.gdb/selftest.exp: backtrace through signal handler (timeout)
>
> Apart of that, no problem seen."
See the description in commit 4a11f2065906, which was later
reverted:
~~~
Sync readline/ to version 7.0 alpha
...
After the sync there is one testsuite regression, the test
"signal SIGINT" in gdb.gdb/selftest.exp which now FAILs. Previously,
the readline 6.2 SIGINT handler would temporarily reinstall the
underlying application's SIGINT handler and immediately re-raise SIGINT
so that the orginal handler gets invoked. But now (since readline 6.3)
its SIGINT handler does not re-raise SIGINT or directly invoke the
original handler; it now sets a flag marking that SIGINT was raised, and
waits until readline explicitly has control to call the application's
SIGINT handler. Anyway, because SIGINT is no longer re-raised from
within readline's SIGINT handler, doing "signal SIGINT" with a stopped
inferior gdb process will no longer resume and then immediately stop the
process (since there is no 2nd SIGINT to immediately catch). Instead,
the inferior gdb process will now just print "Quit" and continue to run.
So with this commit, this particular test case is adjusted to reflect
this change in behavior (we now have to send a 2nd SIGINT manually to
stop it).
~~~
Thanks,
Pedro Alves