Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix to watchthreads test case
Date: Tue, 12 Oct 2004 22:50:00 -0000	[thread overview]
Message-ID: <416C5FA2.7030103@redhat.com> (raw)
In-Reply-To: <416B480B.nail9EC11LX1U@mindspring.com>

Thanks Michael.  Patch checked in and tested on x86-linux and ia64-linux.

-- Jeff J.

Michael Chastain wrote:
> Jeff Johnston writes:
> 
>>After discussing with Andrew, it was suggested that watchthreads.exp be
>>given its own C file which is a copy of schedlock.c.
> 
> 
> Sounds good to me, I like it that way too.
> 
> It looks like I broke this.  :(  When I added a copyright notice to
> schedlock.c, I tested schedlock.exp, but I did not look for any other
> *.exp files that shared schedlock.c.  So I just plain broke it.
> 
> 
>>This new patch replaces the old one below.
>>Hopefully, someone will get a chance to look at it.
> 
> 
> I'm still catching up on my e-mail so maybe Michael Snyder already
> reviewed this patch.  But if not -- I approve this, if you say how
> you tested it.
> 
> Michael
> 
> ===
> 
> 2004-10-04  Jeff Johnston  <jjohnstn@redhat.com>
> 
> 	* gdb.threads/watchthreads.c: New file for use by watchthreads.exp. 
> 
> 	* gdb.threads/watchthreads.exp: Use gdb_get_line_number to find
> 	breakpoint lines and switch to use watchthreads.c.
> 


      reply	other threads:[~2004-10-12 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 21:43 Jeff Johnston
2004-10-04 20:39 ` Jeff Johnston
2004-10-12 14:56   ` Michael Chastain
2004-10-12 22:50     ` Jeff Johnston [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=416C5FA2.7030103@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    --cc=msnyder@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