From: Michael Chastain <mec.gnu@mindspring.com>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Avoid timeouts in call-sc.exp
Date: Thu, 26 Aug 2004 14:17:00 -0000 [thread overview]
Message-ID: <412DF0E9.nail3XH41WLNH@mindspring.com> (raw)
In-Reply-To: <200408251206.41425.pgilliam@us.ibm.com>
> Here is another try.
All right! You got everything but the "synchronize" with an "h".
s/syncronize/synchronize/g, both the ChangeLog entry and the
call-sc.exp code.
In the ChangeLog entry, it should read: "gdb.base/call-sc.exp",
not just "gdb.base/call-sc".
With those changes, this patch is approved, and you can check it in.
Do you have write access to the gdb cvs repository,
or would you like me to check it in for you?
> PS: I only did the ${....} because that seemed to be the usage in
> call-sc.exp.
Yes. So I'm trying to get new code written the simple way but there's
that huge body of old code.
===
2004-08-25 Paul Gilliam <pgilliam@us.ibm.com>
* gdb.base/call-sc: Make sure PC is syncronized after the "return".
next prev parent reply other threads:[~2004-08-26 14:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 21:28 Paul Gilliam
2004-08-18 21:58 ` Michael Chastain
2004-08-20 10:34 ` Michael Chastain
2004-08-20 16:17 ` Paul Gilliam
2004-08-23 21:11 ` Paul Gilliam
2004-08-23 21:55 ` Michael Chastain
2004-08-24 16:15 ` Paul Gilliam
2004-08-24 17:26 ` Michael Chastain
2004-08-24 18:50 ` Paul Gilliam
2004-08-24 18:52 ` Daniel Jacobowitz
2004-08-24 18:55 ` Michael Chastain
2004-08-24 19:14 ` Paul Gilliam
2004-08-25 17:54 ` Paul Gilliam
2004-08-25 18:11 ` Michael Chastain
2004-08-25 18:21 ` Paul Gilliam
2004-08-25 18:52 ` Michael Chastain
2004-08-25 19:08 ` Paul Gilliam
2004-08-26 14:17 ` Michael Chastain [this message]
2004-08-26 16:17 ` Paul Gilliam
2004-08-26 16:26 ` Michael Chastain
2004-08-26 16:34 ` Paul Gilliam
[not found] ` <200408261227.58890.pgilliam@us.ibm.com>
[not found] ` <412E5915.8010401@gnu.org>
2004-08-31 19:30 ` Paul Gilliam
2004-08-31 20:48 ` Paul Gilliam
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=412DF0E9.nail3XH41WLNH@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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