From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: fnasser@redhat.com
Subject: [RFA/testsuite] Shorten the maint.exp symbols tests
Date: Mon, 21 Oct 2002 18:58:00 -0000 [thread overview]
Message-ID: <20021022015852.GA22669@nevyn.them.org> (raw)
Right now maint.exp dumps the contents of all symbols. There's a comment
from Jim that, if the C library has debug info, this can take a long time.
And we bump the timeout way up.
Well, on my test systems it takes longer than just a long time: it takes
about 45 minutes. And the generated files are close to a gigabyte. I think
that's a little bit overkill, don't you? :)
I modified the test to dump just the symbols for the files we're interested
in, and it works quite nicely. This cuts the test time back to a reasonable
amount. Is this change OK?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2002-10-21 Daniel Jacobowitz <drow@mvista.com>
* gdb.base/maint.exp: Only dump symbols from one source file
or objfile.
Index: testsuite/gdb.base/maint.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/maint.exp,v
retrieving revision 1.14
diff -u -p -r1.14 maint.exp
--- testsuite/gdb.base/maint.exp 18 Sep 2002 23:53:52 -0000 1.14
+++ testsuite/gdb.base/maint.exp 13 Oct 2002 22:55:02 -0000
@@ -230,9 +230,9 @@ gdb_expect {
timeout { fail "(timeout) maint print psymbols w/o args" }
}
-send_gdb "maint print psymbols psymbols_output\n"
+send_gdb "maint print psymbols psymbols_output ${srcdir}/${subdir}/${srcfile}\n"
gdb_expect {
- -re "^maint print psymbols psymbols_output\r\n$gdb_prompt $"\
+ -re "^maint print psymbols psymbols_output \[^\n\]*\r\n$gdb_prompt $"\
{
send_gdb "shell ls psymbols_output\n"
gdb_expect {
@@ -272,9 +272,9 @@ gdb_expect {
timeout { fail "(timeout) maint print msymbols w/o args" }
}
-send_gdb "maint print msymbols msymbols_output\n"
+send_gdb "maint print msymbols msymbols_output ${binfile}\n"
gdb_expect {
- -re "^maint print msymbols msymbols_output\r\n$gdb_prompt $"\
+ -re "^maint print msymbols msymbols_output \[^\n\]*\r\n$gdb_prompt $"\
{
send_gdb "shell ls msymbols_output\n"
gdb_expect {
@@ -307,16 +307,13 @@ gdb_expect {
timeout { fail "(timeout) maint print symbols w/o args" }
}
-# This command can legitimately take many minutes to execute. If the
-# executable is dynamically linked, then you get all the debugging
-# info for the entire library --- 89Mb on my system. -jimb
+# Request symbols for one particular source file so that we don't try to
+# dump the symbol information for the entire C library - over 500MB nowadays
+# for GNU libc.
-set old_timeout $timeout
-set timeout 600
-
-send_gdb "maint print symbols symbols_output\n"
+send_gdb "maint print symbols symbols_output ${srcdir}/${subdir}/${srcfile}\n"
gdb_expect {
- -re "^maint print symbols symbols_output\r\n$gdb_prompt $"\
+ -re "^maint print symbols symbols_output \[^\n\]*\r\n$gdb_prompt $"\
{
send_gdb "shell ls symbols_output\n"
gdb_expect {
@@ -340,8 +337,6 @@ gdb_expect {
-re ".*$gdb_prompt $" { fail "maint print symbols" }
timeout { fail "(timeout) maint print symbols" }
}
-
-set timeout $old_timeout
send_gdb "maint print type argc\n"
gdb_expect {
next reply other threads:[~2002-10-22 1:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 18:58 Daniel Jacobowitz [this message]
2002-12-03 7:19 ` Fernando Nasser
2002-12-04 13:52 ` David Carlton
2002-12-04 14:20 ` Daniel Jacobowitz
2002-12-04 14:47 ` David Carlton
2002-12-05 12:50 ` David Carlton
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=20021022015852.GA22669@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnasser@redhat.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