This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 02/13] script language API for GDB: extension.[ch]
- From: Tom Tromey <tromey at redhat dot com>
- To: ludo at gnu dot org (Ludovic CourtÃs)
- Cc: gdb-patches at sourceware dot org, guile-user at gnu dot org
- Date: Tue, 07 Jan 2014 20:17:32 -0700
- Subject: Re: [PATCH v2 02/13] script language API for GDB: extension.[ch]
- Authentication-results: sourceware.org; auth=none
- References: <52a7f3e8 dot e7ed440a dot 1c58 dot 020f at mx dot google dot com> <87vbyffcwu dot fsf at fleche dot redhat dot com> <CAP9bCMQx_pDKsRTDv5h62kqO4==MTJ80XsZ2RYfpzsjDT1u68g at mail dot gmail dot com> <87txdklqk4 dot fsf at gnu dot org> <87r48kkc9g dot fsf at fleche dot redhat dot com> <87eh4krl81 dot fsf at gnu dot org> <87iotvixu4 dot fsf at fleche dot redhat dot com> <87vbxv8kag dot fsf at gnu dot org>
>>>>> "Ludovic" == Ludovic CourtÃs <ludo@gnu.org> writes:
Ludovic> I guess this is another limitation of Guileâs current signal handling
Ludovic> strategy, and something we should fix.
I think it seems reasonable for Guile itself, but yeah, it makes it
harder to integrate into gdb. I was pleasantly surprised that Python's
approach was similar enough to gdb's that we could easily integrate the
two.
The Python approach -- basically just setting a per-signal flag that is
checked in the Python equivalent of SCM_TICK -- might be nice for Guile;
however Guile has better threading support, so some additional work may
be required.
Also, at least for gdb it may make sense to mask SIGINT and SIGCHLD in
new Guile threads, if that is possible.
Tom