From: Taimoor Mirza <tmirza@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: Taimoor Mirza <tmirza@codesourcery.com>
Subject: [PATCH 0/2] Improved variable object invalidation in GDB
Date: Thu, 16 Apr 2015 03:33:00 -0000 [thread overview]
Message-ID: <1429155160-4816-1-git-send-email-tmirza@codesourcery.com> (raw)
Hi,
This patch series improves variable object invalidation in GDB.
This patch has been regression tested on ppc-gnu-linux
and i686 targets using both simulator and real boards.
Taimoor Mirza (2):
Fix varobj updation after symbol removal
Testsuite for varobj updation after symbol removal
gdb/objfiles.c | 19 ++
gdb/testsuite/gdb.mi/mi-var-invalidate.exp | 67 ++++++
gdb/testsuite/gdb.mi/sym-file-lib.c | 26 ++
gdb/testsuite/gdb.mi/sym-file-loader.c | 353 ++++++++++++++++++++++++++++
gdb/testsuite/gdb.mi/sym-file-loader.h | 99 ++++++++
gdb/testsuite/gdb.mi/sym-file-main.c | 84 +++++++
gdb/varobj.c | 37 +++
gdb/varobj.h | 3 +
8 files changed, 688 insertions(+)
create mode 100644 gdb/testsuite/gdb.mi/sym-file-lib.c
create mode 100644 gdb/testsuite/gdb.mi/sym-file-loader.c
create mode 100644 gdb/testsuite/gdb.mi/sym-file-loader.h
create mode 100644 gdb/testsuite/gdb.mi/sym-file-main.c
--
1.7.9.5
next reply other threads:[~2015-04-16 3:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 3:33 Taimoor Mirza [this message]
2015-04-16 3:33 ` [PATCH 2/2] Testsuite for varobj updation after symbol removal Taimoor Mirza
2015-04-17 15:18 ` Vladimir Prus
2015-04-23 8:05 ` Taimoor
2015-04-27 18:53 ` Vladimir Prus
2015-04-27 19:10 ` Vladimir Prus
2015-05-11 13:49 ` Taimoor
2015-05-28 9:52 ` Taimoor
2015-06-05 3:03 ` [PATCH 2/2] [PING]Testsuite " Taimoor
2015-04-16 3:33 ` [PATCH 1/2] Fix " Taimoor Mirza
-- strict thread matches above, loose matches on Subject: below --
2019-10-17 10:03 [PATCH 0/2] Improved variable object invalidation in GDB Raza, Saqlain
2019-10-22 12:54 ` Luis Machado
2019-11-07 7:50 ` Saqlain Raza
2014-06-27 10:14 Taimoor Mirza
2014-07-13 7:49 ` Taimoor
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=1429155160-4816-1-git-send-email-tmirza@codesourcery.com \
--to=tmirza@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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