From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fixes testsuit/gdb.base/annota1.exp
Date: Thu, 07 Apr 2005 17:27:00 -0000 [thread overview]
Message-ID: <200504071025.11668.pgilliam@us.ibm.com> (raw)
ping!
This patch fixes a problem in annota1.exp
First message in annota1.exp thread:
http://sources.redhat.com/ml/gdb-patches/2004-09/msg00349.html
Last message in in annota1.exp thread:
http://sources.redhat.com/ml/gdb-patches/2004-09/msg00374.htm
The annota1.exp patch was put on hold, waiting for a set backtrace patch.
I submitted a set backtrace patch here:
First message in set backtrace thread:
http://sources.redhat.com/ml/gdb-patches/2004-10/msg00261.html
last message in set backtrace thread:
http://sources.redhat.com/ml/gdb-patches/2004-10/msg00443.html
Then, like everyone else, I got involved in other things. But an internal bug system just reminded me these where still pending.
Where do these patches sit now?
-=# Paul #=-
next reply other threads:[~2005-04-07 17:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 17:27 Paul Gilliam [this message]
2005-04-14 19:36 ` Daniel Jacobowitz
2005-04-15 23:03 ` [PATCH] add new .exp file and a 'c' testfile to test backtrace limits etc Paul Gilliam
2005-04-30 18:49 ` Daniel Jacobowitz
2005-05-28 23:42 ` Daniel Jacobowitz
2005-04-15 23:38 ` [PATCH] Fixes testsuit/gdb.base/annota1.exp Paul Gilliam
2005-04-27 15:49 ` Daniel Jacobowitz
2005-04-27 20:02 ` Paul Gilliam
2005-04-15 23:38 ` [PATCH] Fixes testsuit/gdb.base/annota1.exp to deal with 'Breakpoint address adjusted' Paul Gilliam
2005-04-27 15:43 ` Daniel Jacobowitz
2005-04-27 21:47 ` [COMMIT] " Paul Gilliam
-- strict thread matches above, loose matches on Subject: below --
2004-09-21 21:43 [PATCH] Fixes testsuit/gdb.base/annota1.exp Paul Gilliam
2004-09-22 14:01 ` Andrew Cagney
2004-09-22 16:56 ` Paul Gilliam
2004-09-22 19:54 ` Andrew Cagney
2004-09-23 2:13 ` Paul Gilliam
2004-09-23 17:08 ` Michael Chastain
2004-09-23 17:25 ` Michael Chastain
2004-09-23 17:25 ` Michael Chastain
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=200504071025.11668.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--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