Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: schedlock.exp questions
Date: Tue, 07 Sep 2004 12:48:00 -0000	[thread overview]
Message-ID: <413DADDF.9090803@axis.com> (raw)
In-Reply-To: <20040825160315.GA31412@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> Is this native or remote (gdbserver based)?  I have some patches which
> make it substantially more reliable on slow native targets but I
> haven't had enough time to test them properly.  They shouldn't affect
> remote though.

If you think it could have anything at all to do with it, I'd be happy 
to try out your patches.  (Though I don't know where "slow" fits into 
the equation, it most surely applies to my remote target.)

-- 
Orjan Friberg
Axis Communications


      parent reply	other threads:[~2004-09-07 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:51 Orjan Friberg
2004-08-24 14:55 ` Daniel Jacobowitz
2004-08-25 15:11   ` Orjan Friberg
2004-08-25 16:03     ` Daniel Jacobowitz
2004-08-27 13:59       ` Orjan Friberg
2004-08-31 14:41         ` Orjan Friberg
2004-09-07 12:48       ` Orjan Friberg [this message]

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=413DADDF.9090803@axis.com \
    --to=orjan.friberg@axis.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.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