From: Yao Qi <yao@codesourcery.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [patch 0/2] Fixes to gdb.base/dump.exp
Date: Tue, 21 Jun 2011 10:42:00 -0000 [thread overview]
Message-ID: <4E007587.2050304@codesourcery.com> (raw)
In current gdb.base/dump.exp, there are 3 gdb sessions started one by
one, and assuming that symbol addresses doesn't change among these 3 gdb
sessions. However, it is not true on non-MMU processor running uclinux.
In order to make it easier to review my two patches, I'd like to
describe what dump.exp does first. In dump.exp, gdb is started three times,
- 1 Start gdb, and run to checkpoint1. Dump memory into files of
different formats.
- 2 Start gdb, and reload these dump files. Compare results in dump
files are same as them in memory.
- 3 Start gdb, and restore these dump files. Compare results in dump
files are the same them in memory.
--
Yao (é½å°§)
next reply other threads:[~2011-06-21 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 10:42 Yao Qi [this message]
2011-06-21 10:58 ` [patch 1/2] Fixes to gdb.base/dump.exp: get value from address instead of name Yao Qi
2011-06-22 15:45 ` Tom Tromey
2011-06-23 10:28 ` Yao Qi
2011-07-01 14:16 ` Yao Qi
2011-07-01 14:23 ` Tom Tromey
2011-07-01 16:51 ` [committed] " Yao Qi
2011-06-21 11:05 ` [patch 2/2] Fixes to gdb.base/dump.exp: Combine dump and restore in a single session Yao Qi
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=4E007587.2050304@codesourcery.com \
--to=yao@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