From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Pedro Alves <pedro@codesourcery.com>,
luisgpm@linux.vnet.ibm.com, gdb-patches@sourceware.org
Subject: Re: linux native async mode support
Date: Fri, 21 Mar 2008 15:47:00 -0000 [thread overview]
Message-ID: <20080321154734.GL25307@caradoc.them.org> (raw)
In-Reply-To: <18401.50314.796016.448704@kahikatea.snap.net.nz>
On Thu, Mar 20, 2008 at 01:57:30PM +1200, Nick Roberts wrote:
> > It's really a timing issue, and that's why I can't reproduce -- it is
> > timing/host sensitive. So this means this problem isn't related to my
> > patch, but it's a general async issue, that may be visible too in "target
> > async" connected to a gdbserver for example. Although since we're running
> > over a slower link there, nobody was probably seeing it. I don't know
> > enough MI to say if this is according to the spec or not, but it feels like
> > a testsuite deficiency, is it not?
>
> I don't think it's a testsuite deficiency but, coincidentally, Vladimir has
> just been talking about removing the "(gdb) \n" after ^running. This may be
> a good reason to do it.
>
> The patch below fixes the fails that I was seeing in mi-var-child-f.exp.
This seems to be a general async issue, not related specifically to
Linux. So let's address it separately. If you think this patch is
right, could you post it in a new thread with an explanation, please?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-21 15:47 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 [this message]
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
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=20080321154734.GL25307@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--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