This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 4/4] Fix solib-display.exp remote check
- From: Simon Marchi <simon dot marchi at polymtl dot ca>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 02 May 2016 15:52:23 -0400
- Subject: Re: [PATCH 4/4] Fix solib-display.exp remote check
- Authentication-results: sourceware.org; auth=none
- References: <1459912543-15328-1-git-send-email-simon dot marchi at polymtl dot ca> <1459912543-15328-4-git-send-email-simon dot marchi at polymtl dot ca> <570BECA8 dot 3050801 at redhat dot com> <581c3da12dacfd50cfbbe4dbd31a981a at simark dot ca> <a527ce44-6d5d-d2c8-888f-673dc74d16a0 at redhat dot com>
On 2016-05-02 14:28, Pedro Alves wrote:
Thanks for the investigation. I think it'd be nice to
add this info as a comment in the test file.
Thanks,
Pedro Alves
What about:
# This test is currently not supported for stub targets, because it uses
the
# start command (through gdb_start_cmd). In theory, it could be changed
to
# use something else (kill + gdb_run_cmd with a manual breakpoint at
main).
# However, when we try that with the native-gdbserver board, we see that
the
# test fails and gdb outputs this upon connection:
#
# warning: Unable to display "a_global": No symbol "a_global" in
current context.
# warning: Unable to display "b_global": No symbol "b_global" in
current context.
# warning: Unable to display "c_global": No symbol "c_global" in
current context.
#
# This is because the initial stop is done before the shared libraries
are
# loaded. If there were some stub targets for which this use case would
be
# supported, then the test could probably be modified to avoid using
start.