This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug remote/23801] remote target code slowed by unnecessary remote_check_symbols() calls
- From: "simon.marchi at ericsson dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 21 Oct 2018 14:33:10 +0000
- Subject: [Bug remote/23801] remote target code slowed by unnecessary remote_check_symbols() calls
- Auto-submitted: auto-generated
- References: <bug-23801-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23801
Simon Marchi <simon.marchi at ericsson dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simon.marchi at ericsson dot com
--- Comment #1 from Simon Marchi <simon.marchi at ericsson dot com> ---
That would make sense, I believe.
It would be good to give it a test run to make sure this introduces no
regression, with
make check RUNTESTFLAGS="--target_board=native-gdbserver"
and
make check RUNTESTFLAGS="--target_board=native-extended-gdbserver"
It is expected (but not desired) that there are many failures when running the
testsuite, so we usually run the tests without and with the patch, and then
compare the two resulting testsuite/gdb.sum files. More details here:
https://sourceware.org/gdb/wiki/TestingGDB
If this works well, here are the instructions for submitting a patch:
https://sourceware.org/gdb/wiki/ContributionChecklist
--
You are receiving this mail because:
You are on the CC list for the bug.