From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Pedro Alves'" <pedro@codesourcery.com>,
"'gdb-patches@sourceware.org'"
<gdb-patches@sourceware.org>
Subject: RE: [RFC/WIP PATCH v2 01/12] Flip to set target-async on by default
Date: Fri, 23 Dec 2011 18:04:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC578D04E475@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <20111217025910.22456.89111.stgit@localhost6.localdomain6>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Pedro Alves
> Sent: Friday, December 16, 2011 9:59 PM
> To: gdb-patches@sourceware.org
> Subject: [RFC/WIP PATCH v2 01/12] Flip to set target-async on
> by default
>
> This flips "set target-async" to default to on. Marc Khouzam's
> earlier reply (on the v1 series) indicating Eclipse does not use
> target-async for all-stop makes me think it may be prudent to actually
> try this with Eclipse and see what happens. Haven't done that though.
I tried all-stop in Eclipse with target-async on. As expected, things
didn't work. Most notably, the interrupt no longer worked since Eclipse
uses ^C in all-stop.
So, I've just pushed a fix to Eclipse to explicitly set target-async to off
when in all-stop mode. http://bugs.eclipse.org/365471
Note that in Eclipse/CDT, we have two GDB integrations.
The default and the one we work on regularly (DSF-GDB) is the one I fixed.
The older one, almost deprecated, (CDI-GDB), I didn't fix just yet because
it wasn't as simple. Worst case, the user will need to add
set target-async off
in their gdbinit file, if they must use the old integration.
Happy Holidays!
Marc
next prev parent reply other threads:[~2011-12-23 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 2:59 [RFC/WIP I/T sets V2 PATCH 00/14] I/T sets Pedro Alves
2011-12-17 2:59 ` [RFC/WIP PATCH v2 01/12] Flip to set target-async on by default Pedro Alves
2011-12-23 18:04 ` Marc Khouzam [this message]
2011-12-17 2:59 ` [RFC/WIP PATCH v2 03/12] manythreads.exp: Adjust to handle threads appearing/disappearing after "Program received signal SIGFOO" Pedro Alves
2011-12-17 3:00 ` [RFC/WIP PATCH v2 04/12] ia64-sigill.exp: Don't assume there's no infrun output after the prompt Pedro Alves
2011-12-17 3:00 ` [RFC/WIP PATCH v2 07/12] Expand %ITSET% and %THREAD% in " Pedro Alves
2011-12-17 3:00 ` [RFC/WIP PATCH v2 11/12] Default the current itset to the current inferior set (curset) Pedro Alves
2011-12-17 3:05 ` [RFC/WIP PATCH v2 08/12] I/T set support for breakpoints - trigger set, and stop set Pedro Alves
2011-12-17 3:07 ` [RFC/WIP PATCH v2 13/12] Comment out new info breakpoints output, in order to not break the test suite Pedro Alves
2011-12-17 3:08 ` [RFC/WIP PATCH v2 12/12] Default "set schedule-multiple" to on Pedro Alves
2011-12-17 8:49 ` [RFC/WIP PATCH v2 14/12] experiment with "scope" Pedro Alves
2011-12-17 12:35 ` [RFC/WIP PATCH v2 02/14] Implement all-stop on top of a target running non-stop mode Pedro Alves
2011-12-17 12:37 ` [RFC/WIP PATCH v2 05/14] watchthreads-reorder.exp: Don't assume there's no infrun output after the prompt Pedro Alves
2011-12-17 12:37 ` [RFC/WIP PATCH v2 06/14] Add base itsets support Pedro Alves
2011-12-17 12:38 ` [RFC/WIP PATCH v2 09/14] Add I/T set support to most execution commands Pedro Alves
2011-12-17 14:05 ` [RFC/WIP PATCH v2 10/14] Parallel steps, wait for all threads to reach their goal Pedro Alves
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=F7CE05678329534C957159168FA70DEC578D04E475@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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