Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: linux native async mode support
Date: Tue, 01 Apr 2008 14:00:00 -0000	[thread overview]
Message-ID: <20080401133711.GA12753@caradoc.them.org> (raw)
In-Reply-To: <20080322220542.4DF038FC6D@kahikatea.snap.net.nz>

On Sun, Mar 23, 2008 at 10:05:42AM +1200, Nick Roberts wrote:
> Attached below.  I've added [board_info gdb_protocol] == "async" since
> "target async" works after Vladimir's changes.

> # This currently only works with native linux and the async remote protocol.
> if { !([isnative] && [istarget *-linux*]) \
>      && [board_info gdb_protocol] != "async" } then {
>   return
> }

It has to be [board_info target gdb_protocol] or [target_info
gdb_protocol].  Actually, this:

if { !([isnative] && [istarget *-linux*]) \
     && (![target_info exists gdb_protocol] \
         || [target_info gdb_protocol] != "async") } then {

> # The plan is for async mode to become the default but toggle for now.
> set saved_gdbflags $GDBFLAGS
> set GDBFLAGS "-ex \"maint set linux-async on\""

Please append to GDBFLAGS instead of setting it; otherwise you'll lose
-nx and it will read $HOME/.gdbinit.

> #if [istarget "i386-*-linux-gnu"] then {
>     linux_async_tests
> #}

Remove the commented out lines.

Otherwise OK.  Thanks for posting this.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-04-01 13:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  8:11 Pedro Alves
2008-03-14 21:17 ` Daniel Jacobowitz
2008-03-17 16:05   ` Pedro Alves
2008-03-17 22:05     ` Daniel Jacobowitz
2008-03-18 23:27       ` Pedro Alves
2008-03-18 23:58         ` Daniel Jacobowitz
2008-03-21 15:55         ` Daniel Jacobowitz
2008-03-21 17:19           ` Pedro Alves
2008-03-28 14:48             ` Maciej W. Rozycki
2008-03-28 16:07               ` Pedro Alves
2008-03-28 16:13                 ` Daniel Jacobowitz
2008-03-28 16:40                   ` Pedro Alves
2008-03-18  0:06     ` Nick Roberts
2008-03-18 23:28       ` Pedro Alves
2008-03-19  3:59         ` Nick Roberts
2008-03-19 16:25           ` Luis Machado
2008-03-19 23:19             ` Pedro Alves
2008-03-19 23:26               ` Pedro Alves
2008-03-20  1:58               ` Nick Roberts
2008-03-21 15:47                 ` Daniel Jacobowitz
2008-03-21 15:49       ` Daniel Jacobowitz
2008-03-21 23:02         ` Nick Roberts
2008-03-22  1:25           ` Daniel Jacobowitz
2008-03-22 22:06             ` Nick Roberts
2008-04-01 14:00               ` Daniel Jacobowitz [this message]
2008-04-01 15:17               ` Vladimir Prus
2008-04-01 20:09                 ` Nick Roberts
2008-04-04 12:34                   ` Vladimir Prus
2008-04-05 17:20                     ` Nick Roberts
2008-04-05 22:07                       ` Vladimir Prus
2008-04-07  0:06                         ` Nick Roberts
2008-04-07  2:33                         ` Nick Roberts
2008-03-18  2:47     ` Nick Roberts
2008-03-14 23:10 ` Nick Roberts
2008-03-15  1:58   ` Pedro Alves
2008-03-15  3:11     ` Daniel Jacobowitz
2008-03-17 23:41     ` Nick Roberts

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=20080401133711.GA12753@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickrob@snap.net.nz \
    --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